-
Notifications
You must be signed in to change notification settings - Fork 73
Find KSP Configurations that are Added Later #881
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It may be clearer to use
.findByName(cfg)
(which is the nullable version of.getByName()
). I was a bit confused byconfigureEach
since there's no possibility there are ever multiple configurations with the same name, is there?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason I used
configureEach
is because it is live. MeaningconfigureEach
will continue to search for the configuration with the target name and run the operation on the new configuration when it is added even if that configuration is added after this plugin is applied. UsingfindByName
is not live, so it wouldn't solve the issue that this PR is trying to solve. Or am I misunderstanding?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By the way, your point is well taken that
configuraitons.named
will continue searching even after it found the configuration. This is undesirable in terms of performance and code cleanness but shouldn't cause any further issues I think.named { it == cfg }
will just run for each configuration and return false, which should take a negligible amount of time ... Though I do think gradle suffers in terms of performance from all of these observers because gradle introduces lots of overhead into a lot of its operations (like sending events to the IDE for example).See gradle/gradle#16543 , which is the same issue but for tasks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gradle ought to eventually implement something like gradle/gradle#16543 but for any live collection (like the live colleciton of configurations). It would replace the technique I used here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright,thanks for the clarification :)