Remove old configurations - #5198
Merged
Merged
Conversation
Member
|
Is the file I think the Gradle config could be removed quite safely. |
Member
Author
I couldn't find any reference to |
cortinico
approved these changes
Aug 8, 2022
3flex
approved these changes
Aug 9, 2022
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.
I'm opening this as a PR but because it's easier than an Issue in this case.
I think that no one uses this configuration any more. It had sense when all/nearly all the rules didn't have type-solving. But right now configurations like that one have little sense.
If you use these configurations or you think it is worth to keep them just close this PR :)