7

When I edit someone's code block with a language identifier:

Example:

from:

```
def py
```

to:

```python
def py
```

Is that change reflected in the Suggested edits queue in the Inline or side-by-side modes?

Sure, it will be reflected in the side-by-side Markdown mode; but no one will have the time to check an edit in the Markdown content. Especially if the change is not shown in the Inline mode or side-by-side mode.

If someone doesn't see the change on the default side-by-side mode and decides not to view the Markdown, the edit has a chance to be rejected.

Example edit:

default side-by-side mode: side-by-side mode showing no difference

side-by-side markdown mode: side-by-side markdown mode showing added language identifier


Why bother: Language identifiers are a good feature of the Stack Exchange network, and it helps to understand complex code and for beginners - all in all if the OP likes it; if the OP doesn't like it, then the OP can reject it.

13
  • 2
    Syntax highlighting in review queues was disabled due to another bug and not enabled back up to this day. So yes, the chance of rejection when making these edits is high. Unfortunately, nothing we can do apart from pestering SE with "are we there yet?" Sep 8 at 11:58
  • 1
    @OlegValter pestering SE with "are we there yet? Can you post a link of the post case/issue or a pastering? and I would like the post of the bug. Sep 8 at 12:03
  • @Gomesz785 it was a Simpsons reference :) As for the report and the "we disabled it everywhere for now", see this MSO report and staff answer Sep 8 at 12:43
  • @OlegValter the link you provided was a answer to a question - "diff bug". So that "diff bug" was fixed but syntax highlighting on the suggestion queue is disabled by SO because, if SO enable the syntax highlighting on the suggestion queue, the bug will start again? Am I correct? Sep 8 at 13:55
  • Am I correct? did SO disabled syntax highlighting on the suggestion queue because of this "diff bug"? Sep 8 at 13:57
  • Someone already stated of my current problem. Sep 8 at 13:58
  • 1
    "but no one will have the time to check an edit in the Markdown content", then maybe they shouldn't be reviewing. If you don't have the time or are unwilling to spend the time to review the post properly and accurately, then you really shouldn't be reviewing the post. While we appreciate people spending time reviewing, it's more important that the reviews be done accurately than it is that the reviews be done quickly, or even at all.
    – Makyen
    Sep 8 at 14:05
  • @Gomesz785 you are correct in the interpretation, unfortunately - as a "hotfix" for another problem, language highlighting was disabled completely in review queues. Yeah, it's frustrating - used to be an active suggested edits reviewer on SO, but pretty much do none of this these days because the experience is far from perfect for every party involved. Sep 8 at 14:18
  • The best thing you can do in the current situation is described by Luuklag - fix every other issue you see with the post, and describe that you added a language hint (don't say "improved highlighting" or "formatting" - most reviewers will be utterly confused because for them, code blocks will still be colourless) Sep 8 at 14:22
  • see staff response after a couple of reminders today - hopefully we will have it back in 6 to 8 Sep 8 at 15:00
  • " If you don't have the time " @Makyen I am not a moderator blaming someone else for taking my valuable-cheesy-review-time by adding language identifiers. While I solely agrees to your idea, I won't be happy if that was a reply to my statement(which is not an even a statement; I used that for describe the possibility of rejection of such edits) in my question: but no one will have the time to check an edit in the Markdown content Sep 9 at 4:55
  • @oleg your explanation is very simple - thanks for reminding the staff. btw what is "back in 6 to 8 " Sep 9 at 4:57
  • @Gomesz785 ah, that's just an old meme of Meta - means "will likely take an indefinite amount of time" :) Thank Luuklag, though - 'tis them who reminded Kyle about it Sep 9 at 5:01
5

All you need is a good edit description. State in your edit description what was changed, so you could state: "Included language hint X for codeblock."

This will still leave some cases where people didn't read your edit description, and just disapproved because they saw no change, but that is then their fault.

At the same time make your edits as substantial as possible. In this case there are some words in caps, that could be turned to lowercase letters and highlighted by either bold or italics.

1
  • just disapproved because they saw no change, but that is then their fault. if this happens I can just keep adding the same language identifiers until some caring moderator reviews it? Sep 8 at 14:11

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .