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
Formatting nits #30
Comments
It seems like v1.7.0 also no longer includes newlines in the generated HTML between steps in |
@ljharb That was as a result of removing the beautify step from EMD so if the line breaks important to you, file a bug there! |
It looks like the issue was decided in tc39/ecmarkdown#12 - I'm not sure why this particular formatting would be that slow. |
If you want to beautify, beautify the whole document as a post-processing step. Don't build that into the tools. |
Do you have a recommended tool to use? Typically I've found it easiest to beautify during generation of HTML, but super difficult to do reliably after. |
Well, we were already doing it after the generation of the HTML, so you're not going to get anything different. js-beautify is what I used. |
Sounds good, I'll try that, thanks. Update: done in tc39/proposal-string-pad-start-end@c0decde - thanks for the tip |
Not special-casing Completion - Completion{ ... } will link to the term Completion, which seems fine. Just need Completion to have a dfn in the source doc so it ends up in the biblio. See jmdyck/es-spec-emu#6. |
These are all addressed in 2.0.0-beta1 |
As reported by Domenic in tc39/proposal-async-await#59:
The text was updated successfully, but these errors were encountered: