Removed the analysis-options-file input, because dart analyze doesn't support it (fixes #12) #13
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
… support it (fixes zgosalvez#12)
|
Is there a way to point my github workflow at this branch until @zgosalvez merges this into master? |
|
Thank you for your patience and contribution 🙂 You are correct. This was caused by PR #9. |
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.
It seems that dart analyze will always look for analysis_options.yaml and that this is not configurable any more. This pull request solves the problem if you do have a analysis_options.yaml in your repo it doesn't crash on the --options flag (see issue #12).