Export default parse rules, another version #40
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for your contribution (and sorry for the very late reply)! I'm not able to merge your PR since the structure of the project has changed, but I just merged PR #67 which exposes the parse rules. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello Benjamin Bray! Thank you for your work on this plugin. I see that another person made a pull request to export default parse rules, but I figured I'd make a slight tweak to that PR. This doesn't alter any imports unlike the other PR. This pull request simply exports the parse rules from index.ts and rebuilt the dist folder with
npm run build:dist.I think this would be a valuable feature, unless of course the implementation is considered too experimental.
Anyways, thank you for the work you do!