Skip to content

chore(deps): bump kotlininject from 0.6.1 to 0.6.2 #216

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 1 commit into from
Aug 28, 2023

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 28, 2023

Bumps kotlininject from 0.6.1 to 0.6.2.
Updates me.tatarka.inject:kotlin-inject-compiler-ksp from 0.6.1 to 0.6.2

Release notes

Sourced from me.tatarka.inject:kotlin-inject-compiler-ksp's releases.

v0.6.2

[0.6.2] 2023-08-28

Changed

  • Updated kotlin to 1.9.0
  • If a dependency's scope is not found on the component providing it, a better error message is given.
  • Adding a @Provides annotation on an abstract fun or val will now warn that it has no effect.
  • When overriding a method the parent is checked to see if it has a @Provides annotation. This makes the example in the README actually work:
    @NetworkScope abstract class NetworkComponent {
      @NetworkScope @Provides abstract fun api(): Api
    }  
    @Component abstract class RealNetworkComponent : NetworkComponent() {
      // This is now treated as a @Provides even if not annotated directly
      override fun api(): Api = RealApi()
    }

Fixed

  • Typealiases are treated as separate types in multibinding. This is consistent with other uses of typealiases.

    For example:

    typealias MyString = String
    @​Component abstract class MyComponent {
    abstract val stringItems: Set<String>
    abstract val myStringItems: Set<MyString>
    @​Provides @​IntoSet fun stringValue1(): String = "string"
    @​Provides @​IntoSet fun stringValue2(): MyString = "myString"
    }

    stringItems will contain {"string"} and myStringItems will contain {"myString"}.

  • Lambda types now work in set multibindings.

    @Component abstract class MyComponent {
      abstract val lambdaSet: Set<() -> String>
    @​Provides @​IntoSet fun lambda1(): () -> String = { "one" }
    @​Provides @​IntoSet fun lambda2(): () -> String = { "two" }
    }

  • Assisted injection no longer works with scopes or cycles. These two cases would over-cache the instance, ignoring the

... (truncated)

Changelog

Sourced from me.tatarka.inject:kotlin-inject-compiler-ksp's changelog.

[0.6.2] 2023-08-28

Changed

  • Updated kotlin to 1.9.0
  • If a dependency's scope is not found on the component providing it, a better error message is given.
  • Adding a @Provides annotation on an abstract fun or val will now warn that it has no effect.
  • When overriding a method the parent is checked to see if it has a @Provides annotation. This makes the example in the README actually work:
    @NetworkScope abstract class NetworkComponent {
      @NetworkScope @Provides abstract fun api(): Api
    }  
    @Component abstract class RealNetworkComponent : NetworkComponent() {
      // This is now treated as a @Provides even if not annotated directly
      override fun api(): Api = RealApi()
    }

Fixed

  • Typealiases are treated as separate types in multibinding. This is consistent with other uses of typealiases.

    For example:

    typealias MyString = String
    @​Component abstract class MyComponent {
    abstract val stringItems: Set<String>
    abstract val myStringItems: Set<MyString>
    @​Provides @​IntoSet fun stringValue1(): String = "string"
    @​Provides @​IntoSet fun stringValue2(): MyString = "myString"
    }

    stringItems will contain {"string"} and myStringItems will contain {"myString"}.

  • Lambda types now work in set multibindings.

    @Component abstract class MyComponent {
      abstract val lambdaSet: Set<() -> String>
    @​Provides @​IntoSet fun lambda1(): () -> String = { "one" }
    @​Provides @​IntoSet fun lambda2(): () -> String = { "two" }
    }

  • Assisted injection no longer works with scopes or cycles. These two cases would over-cache the instance, ignoring the assisted arguments. They now throw an error instead.

... (truncated)

Commits
  • 134622d Update CHANGELOG, prepare release v0.6.2
  • b5c9d99 Update android docs with latest viewmodel functions
  • 3f09fb2 Check overridden method for provides annotation
  • d10eba0 Reject assisted injection in cycles
  • b235fc1 Improve missing scope error message
  • d27a210 Start new name allocation scope when moving into function calls as
  • 561ffbe Fix compile error when accessing parent scoped dependency in cycle run block
  • dcf3d48 Fix publishing
  • 384edc5 Add a warning for applying a scope on a generated component function or
  • bd5c4ad Disallow scopes on types with assisted injection.
  • Additional commits viewable in compare view

Updates me.tatarka.inject:kotlin-inject-runtime from 0.6.1 to 0.6.2

Release notes

Sourced from me.tatarka.inject:kotlin-inject-runtime's releases.

v0.6.2

[0.6.2] 2023-08-28

Changed

  • Updated kotlin to 1.9.0
  • If a dependency's scope is not found on the component providing it, a better error message is given.
  • Adding a @Provides annotation on an abstract fun or val will now warn that it has no effect.
  • When overriding a method the parent is checked to see if it has a @Provides annotation. This makes the example in the README actually work:
    @NetworkScope abstract class NetworkComponent {
      @NetworkScope @Provides abstract fun api(): Api
    }  
    @Component abstract class RealNetworkComponent : NetworkComponent() {
      // This is now treated as a @Provides even if not annotated directly
      override fun api(): Api = RealApi()
    }

Fixed

  • Typealiases are treated as separate types in multibinding. This is consistent with other uses of typealiases.

    For example:

    typealias MyString = String
    @​Component abstract class MyComponent {
    abstract val stringItems: Set<String>
    abstract val myStringItems: Set<MyString>
    @​Provides @​IntoSet fun stringValue1(): String = "string"
    @​Provides @​IntoSet fun stringValue2(): MyString = "myString"
    }

    stringItems will contain {"string"} and myStringItems will contain {"myString"}.

  • Lambda types now work in set multibindings.

    @Component abstract class MyComponent {
      abstract val lambdaSet: Set<() -> String>
    @​Provides @​IntoSet fun lambda1(): () -> String = { "one" }
    @​Provides @​IntoSet fun lambda2(): () -> String = { "two" }
    }

  • Assisted injection no longer works with scopes or cycles. These two cases would over-cache the instance, ignoring the

... (truncated)

Changelog

Sourced from me.tatarka.inject:kotlin-inject-runtime's changelog.

[0.6.2] 2023-08-28

Changed

  • Updated kotlin to 1.9.0
  • If a dependency's scope is not found on the component providing it, a better error message is given.
  • Adding a @Provides annotation on an abstract fun or val will now warn that it has no effect.
  • When overriding a method the parent is checked to see if it has a @Provides annotation. This makes the example in the README actually work:
    @NetworkScope abstract class NetworkComponent {
      @NetworkScope @Provides abstract fun api(): Api
    }  
    @Component abstract class RealNetworkComponent : NetworkComponent() {
      // This is now treated as a @Provides even if not annotated directly
      override fun api(): Api = RealApi()
    }

Fixed

  • Typealiases are treated as separate types in multibinding. This is consistent with other uses of typealiases.

    For example:

    typealias MyString = String
    @​Component abstract class MyComponent {
    abstract val stringItems: Set<String>
    abstract val myStringItems: Set<MyString>
    @​Provides @​IntoSet fun stringValue1(): String = "string"
    @​Provides @​IntoSet fun stringValue2(): MyString = "myString"
    }

    stringItems will contain {"string"} and myStringItems will contain {"myString"}.

  • Lambda types now work in set multibindings.

    @Component abstract class MyComponent {
      abstract val lambdaSet: Set<() -> String>
    @​Provides @​IntoSet fun lambda1(): () -> String = { "one" }
    @​Provides @​IntoSet fun lambda2(): () -> String = { "two" }
    }

  • Assisted injection no longer works with scopes or cycles. These two cases would over-cache the instance, ignoring the assisted arguments. They now throw an error instead.

... (truncated)

Commits
  • 134622d Update CHANGELOG, prepare release v0.6.2
  • b5c9d99 Update android docs with latest viewmodel functions
  • 3f09fb2 Check overridden method for provides annotation
  • d10eba0 Reject assisted injection in cycles
  • b235fc1 Improve missing scope error message
  • d27a210 Start new name allocation scope when moving into function calls as
  • 561ffbe Fix compile error when accessing parent scoped dependency in cycle run block
  • dcf3d48 Fix publishing
  • 384edc5 Add a warning for applying a scope on a generated component function or
  • bd5c4ad Disallow scopes on types with assisted injection.
  • Additional commits viewable in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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 `kotlininject` from 0.6.1 to 0.6.2.

Updates `me.tatarka.inject:kotlin-inject-compiler-ksp` from 0.6.1 to 0.6.2
- [Release notes](https://github.com/evant/kotlin-inject/releases)
- [Changelog](https://github.com/evant/kotlin-inject/blob/main/CHANGELOG.md)
- [Commits](evant/kotlin-inject@v0.6.1...v0.6.2)

Updates `me.tatarka.inject:kotlin-inject-runtime` from 0.6.1 to 0.6.2
- [Release notes](https://github.com/evant/kotlin-inject/releases)
- [Changelog](https://github.com/evant/kotlin-inject/blob/main/CHANGELOG.md)
- [Commits](evant/kotlin-inject@v0.6.1...v0.6.2)

---
updated-dependencies:
- dependency-name: me.tatarka.inject:kotlin-inject-compiler-ksp
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: me.tatarka.inject:kotlin-inject-runtime
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Changes that affect dependencies gradle Gradle changes labels Aug 28, 2023
@dependabot dependabot bot requested a review from sureshg August 28, 2023 19:47
@github-actions github-actions bot merged commit 4dfae85 into main Aug 28, 2023
@dependabot dependabot bot deleted the dependabot/gradle/kotlininject-0.6.2 branch August 28, 2023 19:47
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Changes that affect dependencies gradle Gradle changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants