-
Notifications
You must be signed in to change notification settings - Fork 143
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
Docs: refine v2-faq.md
and fix a few typos
#1617
Docs: refine v2-faq.md
and fix a few typos
#1617
Conversation
v2-faq.md
v2-faq.md
and fix a few typos
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.
Thanks for working on this!
I just wonder about the manual line breaks added here. Is that something we really still have to do nowadays? Like editors can wrap lines. And if you have explicit line breaks, editing the text can become very tedious, right?
We have prettier explicitly disabled for .md files in this repo. So I think either we set up prettier to do this stuff for us, or we don't care!? Thoughts?
ye, if we merge this I'd like to have this style of formatting be automatic. |
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.
can prettier do this for us?
|
||
```ts | ||
import { Something } from './path/to/file.ts'; | ||
``` | ||
|
||
If you've done ESM in node, this should feel familiar, and we can be be consistent with JS imports as well: | ||
If you've done ESM in node, this should feel familiar, and we can be be consistent with JS imports |
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.
Let's fix be be
.
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.
Me, @mansona and @void-mAlex agree that line breaks add little to no value and cause problems:
- bloated diffs (both for current and upcoming PRs),
- difficulty reading the source for dyslexic people,
- difficulty editing and reformatting.
We believe a paragraph should be a paragraph. You can tweak your IDE for a line wrap (for a specific extension) and preferred line width.
It actually facilitates reading. |
Hey @MrChocolatine 👋 I just want to explain the comment that @lolmaus made a little bit more. We are currently in a meeting for the Embroider Triage and Andrey is "driving" so he expressed an opinion that I had with his comment but it is not exactly clear the reasons for that opinion so I would like to explain a bit better. While you are correct that sentence length is important for facilitating reading, there is a difference between the display of line length and forcing line length by manually (or automatically) putting newlines in the source material. I'm speaking as someone with dyslexia that this sort of forced line break will make it significantly harder for me to read the Markdown source, so much so that I would be forced to read only a rendered output and not be able to easily read diffs in things like github. I personally appreciate the changes that you were making in this PR so I would like to try to get it merged if you wouldn't mind re-opening it and removing the linebreak change? |
As I was reading the changes in #1607 and #1613 (thanks @simonihmig), I took the opportunity to refine a few things on this document.
Initially I spotted a few typos, then decided to improve the overall readability of the document.