Added compile time set binding validation for cases where the same key is bound into a set multiple times. Previously, cases of this could result in a runtime failure due to a similar check at runtime, but in rare cases that don’t trigger the runtime error, this could be a breaking change. (cf2047099)
Bug Fixes
Make nested subcomponents and switching provider impls static within the generated component class. This is in preparation for eventually unnesting these classes from within their parent component to avoid issues that arise from deeply nested class names being too long. (d9f08aa3c)
What’s New in Hilt
Fragment#getContext() behavior fixed behind a flag
Currently, a Hilt fragment’s getContext() method incorrectly continues to return a context value even after the fragment is removed. This differs from the behavior of a regular fragment. Fixing this is a breaking change that may introduce crashes at runtime if code incorrectly accessed the fragment’s context after removal and relied on Hilt’s incorrect behavior, so a flag has been introduced with the new fixed behavior default off.
Please enable the flag with -Adagger.hilt.android.useFragmentGetContextFix=true to roll out this change at your own discretion. You may choose to, for example, start by enabling this only in development or some small testing population to find errors. In a future release, this flag will be defaulted to true and then in some release after that, the flag will be removed. (5ce0ceadd)
Bug Fixes
Fix a bug where a Hilt fragment’s getContext() method could not be called before super.onAttach(). (8acc4336f)
Fix compatibility issue with the Hilt Gradle Plugin and Android Gradle Plugin 7.0 (371a2c366)
Fix lint issue with Hilt testing classes that get compiled to reference invalid ReflectiveOperationException for API < 19. (e58abc3f7)
Added compile time set binding validation for cases where the same key is bound into a set multiple times. Previously, cases of this could result in a runtime failure due to a similar check at runtime, but in rare cases that don’t trigger the runtime error, this could be a breaking change. (cf2047099)
Bug Fixes
Make nested subcomponents and switching provider impls static within the generated component class. This is in preparation for eventually unnesting these classes from within their parent component to avoid issues that arise from deeply nested class names being too long. (d9f08aa3c)
What’s New in Hilt
Fragment#getContext() behavior fixed behind a flag
Currently, a Hilt fragment’s getContext() method incorrectly continues to return a context value even after the fragment is removed. This differs from the behavior of a regular fragment. Fixing this is a breaking change that may introduce crashes at runtime if code incorrectly accessed the fragment’s context after removal and relied on Hilt’s incorrect behavior, so a flag has been introduced with the new fixed behavior default off.
Please enable the flag with -Adagger.hilt.android.useFragmentGetContextFix=true to roll out this change at your own discretion. You may choose to, for example, start by enabling this only in development or some small testing population to find errors. In a future release, this flag will be defaulted to true and then in some release after that, the flag will be removed. (5ce0ceadd)
Bug Fixes
Fix a bug where a Hilt fragment’s getContext() method could not be called before super.onAttach(). (8acc4336f)
Fix compatibility issue with the Hilt Gradle Plugin and Android Gradle Plugin 7.0 (371a2c366)
Fix lint issue with Hilt testing classes that get compiled to reference invalid ReflectiveOperationException for API < 19. (e58abc3f7)
Added compile time set binding validation for cases where the same key is bound into a set multiple times. Previously, cases of this could result in a runtime failure due to a similar check at runtime, but in rare cases that don’t trigger the runtime error, this could be a breaking change. (cf2047099)
Bug Fixes
Make nested subcomponents and switching provider impls static within the generated component class. This is in preparation for eventually unnesting these classes from within their parent component to avoid issues that arise from deeply nested class names being too long. (d9f08aa3c)
What’s New in Hilt
Fragment#getContext() behavior fixed behind a flag
Currently, a Hilt fragment’s getContext() method incorrectly continues to return a context value even after the fragment is removed. This differs from the behavior of a regular fragment. Fixing this is a breaking change that may introduce crashes at runtime if code incorrectly accessed the fragment’s context after removal and relied on Hilt’s incorrect behavior, so a flag has been introduced with the new fixed behavior default off.
Please enable the flag with -Adagger.hilt.android.useFragmentGetContextFix=true to roll out this change at your own discretion. You may choose to, for example, start by enabling this only in development or some small testing population to find errors. In a future release, this flag will be defaulted to true and then in some release after that, the flag will be removed. (5ce0ceadd)
Bug Fixes
Fix a bug where a Hilt fragment’s getContext() method could not be called before super.onAttach(). (8acc4336f)
Fix compatibility issue with the Hilt Gradle Plugin and Android Gradle Plugin 7.0 (371a2c366)
Fix lint issue with Hilt testing classes that get compiled to reference invalid ReflectiveOperationException for API < 19. (e58abc3f7)
Added compile time set binding validation for cases where the same key is bound into a set multiple times. Previously, cases of this could result in a runtime failure due to a similar check at runtime, but in rare cases that don’t trigger the runtime error, this could be a breaking change. (cf2047099)
Bug Fixes
Make nested subcomponents and switching provider impls static within the generated component class. This is in preparation for eventually unnesting these classes from within their parent component to avoid issues that arise from deeply nested class names being too long. (d9f08aa3c)
What’s New in Hilt
Fragment#getContext() behavior fixed behind a flag
Currently, a Hilt fragment’s getContext() method incorrectly continues to return a context value even after the fragment is removed. This differs from the behavior of a regular fragment. Fixing this is a breaking change that may introduce crashes at runtime if code incorrectly accessed the fragment’s context after removal and relied on Hilt’s incorrect behavior, so a flag has been introduced with the new fixed behavior default off.
Please enable the flag with -Adagger.hilt.android.useFragmentGetContextFix=true to roll out this change at your own discretion. You may choose to, for example, start by enabling this only in development or some small testing population to find errors. In a future release, this flag will be defaulted to true and then in some release after that, the flag will be removed. (5ce0ceadd)
Bug Fixes
Fix a bug where a Hilt fragment’s getContext() method could not be called before super.onAttach(). (8acc4336f)
Fix compatibility issue with the Hilt Gradle Plugin and Android Gradle Plugin 7.0 (371a2c366)
Fix lint issue with Hilt testing classes that get compiled to reference invalid ReflectiveOperationException for API < 19. (e58abc3f7)
Added compile time set binding validation for cases where the same key is bound into a set multiple times. Previously, cases of this could result in a runtime failure due to a similar check at runtime, but in rare cases that don’t trigger the runtime error, this could be a breaking change. (cf2047099)
Bug Fixes
Make nested subcomponents and switching provider impls static within the generated component class. This is in preparation for eventually unnesting these classes from within their parent component to avoid issues that arise from deeply nested class names being too long. (d9f08aa3c)
What’s New in Hilt
Fragment#getContext() behavior fixed behind a flag
Currently, a Hilt fragment’s getContext() method incorrectly continues to return a context value even after the fragment is removed. This differs from the behavior of a regular fragment. Fixing this is a breaking change that may introduce crashes at runtime if code incorrectly accessed the fragment’s context after removal and relied on Hilt’s incorrect behavior, so a flag has been introduced with the new fixed behavior default off.
Please enable the flag with -Adagger.hilt.android.useFragmentGetContextFix=true to roll out this change at your own discretion. You may choose to, for example, start by enabling this only in development or some small testing population to find errors. In a future release, this flag will be defaulted to true and then in some release after that, the flag will be removed. (5ce0ceadd)
Bug Fixes
Fix a bug where a Hilt fragment’s getContext() method could not be called before super.onAttach(). (8acc4336f)
Fix compatibility issue with the Hilt Gradle Plugin and Android Gradle Plugin 7.0 (371a2c366)
Fix lint issue with Hilt testing classes that get compiled to reference invalid ReflectiveOperationException for API < 19. (e58abc3f7)
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.
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 squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor 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)
Bumps
dagger_versionfrom 2.35 to 2.36. Updateshilt-android-gradle-pluginfrom 2.35 to 2.36Release notes
Sourced from hilt-android-gradle-plugin's releases.
Commits
32b4f902.36 release5ce0ceaAdds the dagger.hilt.android.useFragmentGetContextFix flag to guard the corre...9bfc67eTemporarily hide the 'enableAggregatingTask' option.6bd3c6eGroup BindingExpression and CreationExpression factories into UnscopedDirectI...266100eEnable Gradle config cache in test projects when AGP is 4.2.0+935a437Refactor BindingExpressions and CreationExpressions to use assisted injection.8bba02fUse WorkerApi in HiltGradlePlugin's AggregateDepsTaskefcf848Update Hilt incremental processor tests to verify isolating and aggregating t...0057216Share aggregating logic between RootProcessor and Gradle plugin.f227774Add the concept of ShardImplementation.Updates
daggerfrom 2.35 to 2.36Release notes
Sourced from dagger's releases.
Commits
32b4f902.36 release5ce0ceaAdds the dagger.hilt.android.useFragmentGetContextFix flag to guard the corre...9bfc67eTemporarily hide the 'enableAggregatingTask' option.6bd3c6eGroup BindingExpression and CreationExpression factories into UnscopedDirectI...266100eEnable Gradle config cache in test projects when AGP is 4.2.0+935a437Refactor BindingExpressions and CreationExpressions to use assisted injection.8bba02fUse WorkerApi in HiltGradlePlugin's AggregateDepsTaskefcf848Update Hilt incremental processor tests to verify isolating and aggregating t...0057216Share aggregating logic between RootProcessor and Gradle plugin.f227774Add the concept of ShardImplementation.Updates
dagger-compilerfrom 2.35 to 2.36Release notes
Sourced from dagger-compiler's releases.
Commits
32b4f902.36 release5ce0ceaAdds the dagger.hilt.android.useFragmentGetContextFix flag to guard the corre...9bfc67eTemporarily hide the 'enableAggregatingTask' option.6bd3c6eGroup BindingExpression and CreationExpression factories into UnscopedDirectI...266100eEnable Gradle config cache in test projects when AGP is 4.2.0+935a437Refactor BindingExpressions and CreationExpressions to use assisted injection.8bba02fUse WorkerApi in HiltGradlePlugin's AggregateDepsTaskefcf848Update Hilt incremental processor tests to verify isolating and aggregating t...0057216Share aggregating logic between RootProcessor and Gradle plugin.f227774Add the concept of ShardImplementation.Updates
hilt-androidfrom 2.35 to 2.36Release notes
Sourced from hilt-android's releases.
Commits
32b4f902.36 release5ce0ceaAdds the dagger.hilt.android.useFragmentGetContextFix flag to guard the corre...9bfc67eTemporarily hide the 'enableAggregatingTask' option.6bd3c6eGroup BindingExpression and CreationExpression factories into UnscopedDirectI...266100eEnable Gradle config cache in test projects when AGP is 4.2.0+935a437Refactor BindingExpressions and CreationExpressions to use assisted injection.8bba02fUse WorkerApi in HiltGradlePlugin's AggregateDepsTaskefcf848Update Hilt incremental processor tests to verify isolating and aggregating t...0057216Share aggregating logic between RootProcessor and Gradle plugin.f227774Add the concept of ShardImplementation.Updates
hilt-compilerfrom 2.35 to 2.36Release notes
Sourced from hilt-compiler's releases.
Commits
32b4f902.36 release5ce0ceaAdds the dagger.hilt.android.useFragmentGetContextFix flag to guard the corre...9bfc67eTemporarily hide the 'enableAggregatingTask' option.6bd3c6eGroup BindingExpression and CreationExpression factories into UnscopedDirectI...266100eEnable Gradle config cache in test projects when AGP is 4.2.0+935a437Refactor BindingExpressions and CreationExpressions to use assisted injection.8bba02fUse WorkerApi in HiltGradlePlugin's AggregateDepsTaskefcf848Update Hilt incremental processor tests to verify isolating and aggregating t...0057216Share aggregating logic between RootProcessor and Gradle plugin.f227774Add the concept of ShardImplementation.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.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 squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor 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)