Fix annoying warnings in IntelliJ #2918
Merged
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
Kover Report
|
|
2023 IDEA build fixes the DSL SCOPE issue, we could remove it soon |
JavierSegoviaCordoba
approved these changes
Feb 3, 2023
franciscodr
approved these changes
Feb 4, 2023
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.
This PR is mostly for those developing Arrow within IntelliJ. If you open any build file, you get quite some errors, which can be easily suppressed. This PR does exactly so.
In addition, calls to
forUseAtConfigurationTimeare removed. This method is deprecated, and should just be dropped.With this, one can open the project in IntelliJ without spurious errors.