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

build(deps): bump dagger-compiler from 2.16 to 2.21 #168

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps dagger-compiler from 2.16 to 2.21.

Release notes

Sourced from dagger-compiler's releases.

Dagger 2.21

  • Build performance improvements (174a7a9b)
    • Separately, there may be an increase in build times for opensource users using javac9 or javac10. Neither javac8 or javac11 should be affected. (96fcce89)
  • New validation:
    • Installing a module with scoped bindings that an ancestor component has also installed is now an error. (4695ff51)
    • A warning is now reported if an explicit binding conflicts with an [**Inject**](https://github.com/Inject) binding in an ancestor component. This was never intended to be supported but never checked. Adds a flag to control whether that is a warning or an error. (7f5500fb)
    • Installing a [**ProducerModule**](https://github.com/ProducerModule) in a [**Subcomponent**](https://github.com/Subcomponent) that is already installed in a parent (or earlier ancestor) component is now an error. It is also an error to repeat a [**Module**](https://github.com/Module) that has a binding in [**ProductionScope**](https://github.com/ProductionScope). (68b21537)
  • SPI
    • New method: ComponentNode.isSubcomponent() (b6b9dcac)
  • Producers
    • Deprecated dagger.producers.internal.Producers.immediateProducer() and dagger.producers.internal.Producers.immediateFailedProducer() in favor of newly added methods with the same names in dagger.producers.Producers (a4914c61) (added in 50d7010f)
  • Properly generate components when qualifiers are generated (ab9cdbc2)
  • Dagger itself now uses more Dagger (97fce1e3)

Dagger 2.20

  • Peformance improvements in annotation processing (8012ab5c)
  • Report duplicate bindings only once, not once per request. (623461fb)
  • Make sure all processing steps defer elements properly if they have missing types. (3b0fcc82)
  • Make [**ProductionComponent**](https://github.com/ProductionComponent) have runtime retention so tools can interpret it like all of the other component annotations (fff65e3c)
  • 325b516a:
    • Add module-level validation. When -Adagger.moduleBindingValidation=ERROR or =WARNING is set, then each module is processed as a kind of component (without generating any code) in order to validate the bindings installed by it and all included modules. Any binding graph errors, such as duplicate bindngs (but not including missing bindings), will be reported as errors or warnings depending on the option.
  • Report map multibinding contribution errors once regardless of whether the map is requested as Map<K, V>, Map<K, Provider<V>>, or Map<K, Producer<V>>. (350368e6)
  • c7e7c4f1:
    • Fixes two bugs related to [**ProductionScope**](https://github.com/ProductionScope) bindings:
      • Where modules with [**ProductionScope**](https://github.com/ProductionScope) bindings are installed in multiple components in the same component ancestry, the binding is now resolved only once and only in the rootmost component.
      • When [**Inject**](https://github.com/Inject) bindings with [**ProductionScope**](https://github.com/ProductionScope) are referenced in a binding graph, the binding is now resolved in the rootmost ProductionScope component.
  • 221f000e:
    • dagger.android code can no longer use the AndroidInjector.Factory<? extends Activity> format to bind injector factories. See https://google.github.io/dagger/android and the 2.19 release notes for information on how to migrate.
    • Adds an ErrorProne refactoring for migrating from AndroidSupportInjectionModule (which now is functionless) to AndroidInjectionModule. See these docs for how to apply the refactoring to your codebase if you're on dagger-compiler-2.20.
  • Removed dagger.releaseablereferences (a72c3428)
  • Removed the -Adagger.floatingBindsMethods flag added in 2.17 (https://github.com/google/dagger/wiki/Dagger-2.17-@Binds-bugs) (bc8dd5bd)

Dagger 2.19

  • dagger.android has a new format for binding AndroidInjector.Factorys:
    • Instead of returning AndroidInjector.Factory<? extends Activity> (or Service, Fragment, etc), return just AndroidInjector.Factory>
    • Instead of using [**ActivityKey**](https://github.com/ActivityKey) (or [**ServiceKey**](https://github.com/ServiceKey), [**FragmentKey**](https://github.com/FragmentKey), etc), use [**ClassKey**](https://github.com/ClassKey). The dagger.android map keys (with the exception of [**AndroidInjectionKey**](https://github.com/AndroidInjectionKey) are now deprecated
    • If you use [**ContributesAndroidInjector**](https://github.com/ContributesAndroidInjector), there's nothing to do. We have updated the output to match the new format
    • We have provided an ErrorProne refactoring for migrating to the new format of binding AndroidInjector.Factorys with dagger.android. See these docs for how to apply the refactoring to your codebase if you're on dagger-compiler-2.19. (02dc4a7f)
    • In the next release (2.20), we will remove the old format. This will allow us to support AndroidX packages better.
    • For the complete docs, visit https://google.github.io/dagger/android
  • Avoid some thrown errors during Dagger compilation for invalid modules. (4df5adf9)
  • Some formatting fixes even when the formatter is turned off

Dagger 2.18

  • Producers:
    • Added [**CancellationPolicy**](https://github.com/CancellationPolicy) annotation, which can be used to make a production component or subcomponent allow cancellation of its subcomponent(s) to propagate up to it and cancel its nodes as well. (f5c04a54)
    • Producer cancellation is now deterministic; cancelling an entry point of a production component will now ensure that it cancels all running tasks for that component and prevents any further tasks for that component from starting. For components with more than one entry point, this does mean that cancelling one entry point will cancel all entry points for the component. For production subcomponents, cancellation of a subcomponent entry point will not propagate cancellation to tasks owned by an ancestor component. (ea48dfd4)
  • Better Errors:
    • Change constructor bindings and dependency requests from void package.Class.<init>(params) to package.Class(params), which looks more like how Java users think of constructors. (d31943c2)
    • Report errors on members injection component methods and MembersInjector requests that have qualifiers. (3be3073f)
... (truncated)
Commits
  • 556f2ab 2.21 release
  • e0e47f1 Fix the GenerationOptions retrieval and enable a build_test for the dagger.f...
  • 13f0cbe Explicitly tell BindingGraphConverter whether it's creating a full binding gr...
  • e6215df Fix coverage runs
  • 4612457 Propagate compiler options related to generation from a base implementation t...
  • 6000d48 A few more minor changes to ComponentCreatorImplementation(Factory) and Compo...
  • fed0de5 Somewhat hacky fix for issue with missing paramters in AOTS configureInitiali...
  • b6b9dca Change isPartialBindingGraph() to look at the root component.
  • 0be7193 Make component requirement fields come first in a component.
  • fe232f5 Simplify ComponentCreatorImplementationFactory.maybeReturnThis()
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking Bump now in your Dependabot dashboard.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

Bumps [dagger-compiler](https://github.com/google/dagger) from 2.16 to 2.21.
- [Release notes](https://github.com/google/dagger/releases)
- [Changelog](https://github.com/google/dagger/blob/master/CHANGELOG.md)
- [Commits](google/dagger@dagger-2.16...dagger-2.21)

Signed-off-by: dependabot[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Jan 22, 2019
luk1337 pushed a commit to luk1337/WykopMobilny that referenced this pull request Dec 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant