You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This rule came to mind when running into a Prettier bug with links that have HTTP encoding in them. It would be awesome to see a rule that prevents HTTP encoding within links -- since browsers automatically re-encode links as needed, it would also help with readability when looking at the raw Markdown.
For example, /fr/docs/Web/JavaScript/Tableaux_typ%C3%A9s would be disallowed and must be converted to /fr/docs/Web/JavaScript/Tableaux_typés.
(I can also see the possibility of a configuration option that inverts this rule, so that links must be HTTP encoded, but in a world where Unicode exists, I doubt this option would have much benefit.)
Edit: I realize that %20 is actually a good case of where HTTP encoding should be used. Maybe a configurable allow list should be a thing?
The text was updated successfully, but these errors were encountered:
This rule came to mind when running into a Prettier bug with links that have HTTP encoding in them. It would be awesome to see a rule that prevents HTTP encoding within links -- since browsers automatically re-encode links as needed, it would also help with readability when looking at the raw Markdown.
For example,
/fr/docs/Web/JavaScript/Tableaux_typ%C3%A9s
would be disallowed and must be converted to/fr/docs/Web/JavaScript/Tableaux_typés
.(I can also see the possibility of a configuration option that inverts this rule, so that links must be HTTP encoded, but in a world where Unicode exists, I doubt this option would have much benefit.)
Edit: I realize that
%20
is actually a good case of where HTTP encoding should be used. Maybe a configurableallow
list should be a thing?The text was updated successfully, but these errors were encountered: