Expose configuration exceptions in scalafmt#836
Merged
nedtwigg merged 4 commits intodiffplug:mainfrom Apr 8, 2021
Merged
Conversation
Member
|
LGTM! Update all 3 changelogs, run |
Member
Contributor
Author
Sorry about that @nedtwigg, all green now :). By the way, thanks for all the hard work and making spotless available for anyone to use. |
Member
|
Thanks for the contribution! Publishing is gunked up atm due to the jcenter sunset, but it'll get published by tomorrow. |
Member
|
Released in |
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
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.
Read scalafmt configuration in a way that shows parsing errors.
Before this change invalid scalafmt configuration files would fail like this:
With this change any exceptions from scalafmt configuration parsing will be visible, for example:
Resolves #837