feat(cli): added parser arg #2842
Open
Conversation
This file contains hidden or 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
Author
|
Reopened #2737 upon request from @sbstnkr. I was not able to run tests locally (in devcontainer) due to headless Chrome not being installed. I can install it manually, but shouldn't the devcontainer include everything needed? |
Author
|
I'm also getting failed lint tests, but they also fail on the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #[ISSUE_NUMBER].
Checklist
Does this PR introduce a breaking change?
Additional context
Suggestion for adding support for a parser argument to the CLI so that the appropriate parser can be selected for Json files. Reopened from #2737