ecmarkup icon indicating copy to clipboard operation
ecmarkup copied to clipboard

An HTML superset/Markdown subset source format for ECMAScript and related specifications

Results 98 ecmarkup issues
Sort by recently updated
recently updated
newest added

All of the following seems annoying to have to maintain in my source file: ``` html ``` Should Ecmarkup generate these for me? It already generates `` I noticed. I...

feature

http://services.w3.org/htmldiff is OK except it disallows "invalid" (custom) elements. http://www.w3.org/wiki/HtmlDiff contains a good list of possibilities An example output is http://services.w3.org/htmldiff?doc1=https%3A%2F%2Frawgit.com%2Fwhatwg%2Ffetch%2F53c071b078bf345aaad7e9cbf2d1d425d53c82ef%2FOverview.html&doc2=https%3A%2F%2Ffetch.spec.whatwg.org%2F ([example section with a few inline changes](http://services.w3.org/htmldiff?doc1=https%3A%2F%2Frawgit.com%2Fwhatwg%2Ffetch%2F53c071b078bf345aaad7e9cbf2d1d425d53c82ef%2FOverview.html&doc2=https%3A%2F%2Ffetch.spec.whatwg.org%2F#concept-http-fetch))

feature

Based on an off-line discussion, I thought that ``` Foo Bar Baz ``` might at some point result in `` tags around `Bar` and `Baz`. Instead, it seems that, as...

feature

https://resources.whatwg.org/file-issue.js In action: https://url.spec.whatwg.org/ or other specs Would be great to be able to report issues easily in Ecmarkup specs.

feature

http://tc39.github.io/ecmascript-asyncawait/#AsyncFunctionDeclaration-static-semantics could be prettier: ![screenshot 31](https://cloud.githubusercontent.com/assets/617481/7869072/fd32a080-0545-11e5-949c-fb138004483a.png) Some ideas (brainstorming): - Don't allow breaking in component parts, e.g. "[no LineTerminator here]" should always stay on one line. - New line and...

feature

At least some lint rules which predate the formatter - notably "no more than one blank line is allowed" - could be handled by running the formatter with `--check`. We...

This way we can mark it non-optional.

linting

cf. https://github.com/tc39/ecma262/pull/2912 It would ideally be configurable and/or suppressible, because ECMA-262 maintains a grammar summary but I don't think _every_ spec does.

feature

When I accidentally write `&lte;` when I mean `≤`, ecmarkup should complain.

content should be: https://github.com/Jack-Works/ecmarkup-language-service/blob/main/language-server/src/biblio.d.ts the name should be `biblio.d.json.ts` iirc