Skip to content
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

Deffer accessing to apollo extension properties until task execution #979

Merged

Conversation

sav007
Copy link
Contributor

@sav007 sav007 commented Jul 8, 2018

The issue has been discovered with plain java projects that seems gradle evaluate differently than android projects. All plugin configuration extension properties were ignored because they were accessing too soon. This PR wraps plugin extension properties with Property class to provide lazy evaluation for tasks during their execution. By using Property wrapper the min required version of gradle is bumped to 4.3+. Some classes were converted back to groovy, that is done intentionally as there is some black magic is going on by gradle generating additional code for properties.

This PR fixes another issue generated files for removed graphql queries are not deleted.

The issue has been discovered with plain java projects that seems gradle evaluate differently than android projects. All plugin configuration extension properties were ignored because they were accessing too soon. This PR wraps plugin extension properties with `Property` class to provide lazy evaluation for tasks during their execution. By using `Property` wrapper the min required version of gradle is bumped to 4.+. Some classes were converted back to groovy, that is done intentionally as there is some `black magic` is going on by gradle generating additional code for properties.
@sav007 sav007 force-pushed the bug/gradle-lazy-property-evaluation branch from 4c420a3 to a643126 Compare July 17, 2018 03:50
@sav007 sav007 merged commit 37d3f8c into apollographql:master Jul 23, 2018
@sav007 sav007 deleted the bug/gradle-lazy-property-evaluation branch July 23, 2018 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants