Use Lazy APIs in Tasks #396
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
rpalcolea
force-pushed
the
use-lazy-apis
branch
from
049f9f5 to
e3bc4cd
Compare
rpalcolea
added a commit
that referenced
this pull request
Nov 21, 2023
* Introduce BaseIntegrationTestKitSpec * FindMethodReferencesSpec: use BaseIntegrationTestKitSpec * MultiProjectCircularDependencyRuleSpec: use BaseIntegrationTestKitSpec * Use lazy registration for lintGradleTask * FixGradleLintTask: use lazy apis * GradleLintReportTask.groovy: use lazy apis
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 introduces lazy APIs for tasks and
BaseIntegrationTestKitSpecfor the futureMOving this to config cache ready will be interesting as we use the
projectobject a lot