-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#3 - Preserve Markdown trailing whitespace #4
Conversation
✅ Deploy Preview for tftmap-massive-wiki ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
@AramZS, I think the (I'm guessing WDYT? |
@peterkaminski It depends on what editor the user is using! I have an additional configuration at the editor level that handles it, but not all users might. I'm fine switching it over to 2 spaces / tab (though that is not my personal preference), but we should be prepared to have some big changesets every time someone touches an older file, at least for a while until the editors' autofix smooth out all the changes. |
As per the discussion, this is now two spaces === tab in markdown in order to support wide editor use and configuration using editorconfig. |
See for most notable reference: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, thanks for the consideration and research, Aram!
I was not aware that line-breaks were created with a double space at the end of a line. Very cool! Updated rules to preserve this technique.
Figured I'd also get ahead of potential YAML use and add rules to preserve its requirements as well.
Should resolve most of #3