Skip to content
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

Merge 1.3 branch in as v2.0.0 #256

Merged
merged 91 commits into from
May 28, 2022
Merged

Merge 1.3 branch in as v2.0.0 #256

merged 91 commits into from
May 28, 2022

Conversation

hildjj
Copy link
Contributor

@hildjj hildjj commented May 28, 2022

Version 2.0.0 complete.

Mingun and others added 30 commits October 18, 2021 00:52
Such joins stringify SourceNode's prematurally
Again, this prevents premature stringification of the SourceNodes
Regenerate parser, add documentation and tests
… be written

Also exit with error code 2 when CLI fails because of invalid test input
and update CLI tests to check exit code
Character class description contains redundant commas between class parts:

[1,2,3-5] instead of [123-5] for class [123-5]
Add example grammars for XML and source-mapping:mapping
Fix a regression in the description of character classes in error message
* main:
  Update link to minified code.  TODO: automate
@hildjj hildjj merged commit edec7a0 into main May 28, 2022
@hildjj hildjj deleted the 1.3 branch May 28, 2022 17:07
@Mingun
Copy link
Member

Mingun commented Jun 1, 2022

@hildjj, could you restore 1.3 branch? Then it would be possible for me to retarget PRs to a main branch, as explained here. Then it can be deleted again :). I prefer to keep discussions about proposed features in single PR.

@hildjj hildjj restored the 1.3 branch June 1, 2022 16:34
@hildjj
Copy link
Contributor Author

hildjj commented Jun 1, 2022

Done. It turns out I hadn't deleted 1.3 from my own repo, so I checked that out, then pushed it upstream.

@Mingun
Copy link
Member

Mingun commented Jun 1, 2022

Nice. Probably need to reopen PRs -- I cannot do that myself. Could you please reopen #206, #208 and #240?

@hildjj
Copy link
Contributor Author

hildjj commented Jun 1, 2022

I got #206 and #240, but #208 has a problem, annotated there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants