The 'under 6 characters' limit on suggested edits should be waived for edits in URLs -- it should be possible to correct something like a trailing slash without messing with the prose.

  • 1
    Correct a trailing slash? How does that make any difference in the URL?
    – mmyers
    Mar 30 '11 at 15:30
  • 4
    @mmyers There's no strict reason that http://example.com/test has to serve the same content as http://example.com/test/. They're different URLs. Most sites tend to cope gracefully with both, either correcting one to the other (usually adding a trailing slash) or serving the same content, but they don't have to, and some don't. A real-world example: uniquesentence.com/sentence/browse works, uniquesentence.com/sentence/browse is a 404. (I must get round to fixing that!) Mar 30 '11 at 15:46
  • 4
    Same problem when fixing a syntax error in a code example: Original poster writes a one-character syntax error. Sometimes it is besides the point to discuss this error and I just want to fix it. The six-character rule should trigger a warning, rather than blocking my edit.
    – Philippe
    May 15 '11 at 13:06
  • 1
    @Philippe: Agreed. If you want to encourage people to make more substantive edits, a warning would do that. The current rule prohibits people from making helpful edits.
    – endolith
    Feb 1 '12 at 16:02
  • I agree per my Q meta.stackexchange.com/questions/126099/…
    – mark
    Mar 20 '12 at 13:06

For example post How to run a specific NUnit test from code using NUnit 3 (C#)

The maintainers moved the uri from ../dev/.. to ../doc/.. for example and the edit failed with the 6 char requirement.

This means the edit has to be 'coerced'.

You must log in to answer this question.

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