Bump kotlinInject from 0.6.3 to 0.7.1

[dependabot[bot]]

Bumps kotlinInject from 0.6.3 to 0.7.1. Updates me.tatarka.inject:kotlin-inject-compiler-ksp from 0.6.3 to 0.7.1

Release notes

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

0.7.1

[0.7.1] 2024-06-12

Fixed

• Removed erroneous @KmpComponentCreator annotation.

0.7.0

[0.7.0] 2024-06-12

Changed

• @Scope annotations now take arguments into account. This means for example, if you have

  @Scope
  annotation class NamedScope(val value: String)
  

  then the scope: @NamedScope("one") and @NamedScope("two") would be treated as distinct. Previously they were treated as the same scope.
• Legacy implicit assisted injection (not using the @Assisted annotation) is now an error.
• The build will now fail if multiple qualifiers are applied in the same place, instead of picking the first one. This applies both to the new annotation (see below) and javax.inject.Qualifier. A minor exception is you are allowed to have one of each type to aid in migration. In that case the me.tatarka.inject one will be chosen.

Added

• Added a me.tatarka.inject.annotations.Qualifier annotation as an alternative to using typealias. For example, you could do:

  @Qualifier
  annotation class Named(val value: String) 
  @​Inject
  class MyClass(@​Named("one") val one: String, @​Named("two") val two: String)
  @​Component
  abstract class MyComponent {
  abstract val myClass: MyClass
  @​Provides @​Named("one")
  fun provideOne(): String = "one"
  @​Provides @​Named("two")
  fun provideTwo(): String = "two"
  }
  

  This behaves the same as javax.inject.Qualifier does when you have me.tatarka.inject.enableJavaxAnnotations=true.
• Added a new @KmpComponentCreate annotation for nicer multiplatform support. This allows you to create component instances from common code when generating platform-specific outputs.

  // src/commonMain
  @Component
  

... (truncated)

Changelog

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

[0.7.1] 2024-06-12

Fixed

• Removed erroneous @KmpComponentCreator annotation.

[0.7.0] 2024-06-12

Changed

• @Scope annotations now take arguments into account. This means for example, if you have

  @Scope
  annotation class NamedScope(val value: String)
  

  then the scope: @NamedScope("one") and @NamedScope("two") would be treated as distinct. Previously they were treated as the same scope.
• Legacy implicit assisted injection (not using the @Assisted annotation) is now an error.
• The build will now fail if multiple qualifiers are applied in the same place, instead of picking the first one. This applies both to the new annotation (see below) and javax.inject.Qualifier. A minor exception is you are allowed to have one of each type to aid in migration. In that case the me.tatarka.inject one will be chosen.

Added

• Added a me.tatarka.inject.annotations.Qualifier annotation as an alternative to using typealias. For example, you could do:

  @Qualifier
  annotation class Named(val value: String) 
  @​Inject
  class MyClass(@​Named("one") val one: String, @​Named("two") val two: String)
  @​Component
  abstract class MyComponent {
  abstract val myClass: MyClass
  @​Provides @​Named("one")
  fun provideOne(): String = "one"
  @​Provides @​Named("two")
  fun provideTwo(): String = "two"
  }
  

  This behaves the same as javax.inject.Qualifier does when you have me.tatarka.inject.enableJavaxAnnotations=true.
• Added a new @KmpComponentCreate annotation for nicer multiplatform support. This allows you to create component instances from common code when generating platform-specific outputs.

  // src/commonMain
  @Component
  abstract class MyKmpComponent
  

... (truncated)

Commits

• a6377f8 Bump version for release
• 3d4d374 remove erroneous @​KmpComponentCreator annotation
• 56aa199 bump version for dev
• 9a91124 prepare release 0.7.0
• 068af05 Allows annotating types with a qualifier
• 701021a fix generated code for scoped lazy circular dependency (#313)
• 6fd78d2 Don't reuse symbols between rounds (#393)
• 8a67444 Use stable nodejs v22
• 3f812c4 Update the generated filename for KmpComponentCreate functions (#385)
• 4c64d32 Add a new annotation to generate Component accessors for KMP targets (#370)
• Additional commits viewable in compare view

Updates me.tatarka.inject:kotlin-inject-runtime from 0.6.3 to 0.7.1

Release notes

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

0.7.1

[0.7.1] 2024-06-12

Fixed

• Removed erroneous @KmpComponentCreator annotation.

0.7.0

[0.7.0] 2024-06-12

Changed

• @Scope annotations now take arguments into account. This means for example, if you have

  @Scope
  annotation class NamedScope(val value: String)
  

  then the scope: @NamedScope("one") and @NamedScope("two") would be treated as distinct. Previously they were treated as the same scope.
• Legacy implicit assisted injection (not using the @Assisted annotation) is now an error.
• The build will now fail if multiple qualifiers are applied in the same place, instead of picking the first one. This applies both to the new annotation (see below) and javax.inject.Qualifier. A minor exception is you are allowed to have one of each type to aid in migration. In that case the me.tatarka.inject one will be chosen.

Added

• Added a me.tatarka.inject.annotations.Qualifier annotation as an alternative to using typealias. For example, you could do:

  @Qualifier
  annotation class Named(val value: String) 
  @​Inject
  class MyClass(@​Named("one") val one: String, @​Named("two") val two: String)
  @​Component
  abstract class MyComponent {
  abstract val myClass: MyClass
  @​Provides @​Named("one")
  fun provideOne(): String = "one"
  @​Provides @​Named("two")
  fun provideTwo(): String = "two"
  }
  

  This behaves the same as javax.inject.Qualifier does when you have me.tatarka.inject.enableJavaxAnnotations=true.
• Added a new @KmpComponentCreate annotation for nicer multiplatform support. This allows you to create component instances from common code when generating platform-specific outputs.

  // src/commonMain
  @Component
  

... (truncated)

Changelog

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

[0.7.1] 2024-06-12

Fixed

• Removed erroneous @KmpComponentCreator annotation.

[0.7.0] 2024-06-12

Changed

• @Scope annotations now take arguments into account. This means for example, if you have

  @Scope
  annotation class NamedScope(val value: String)
  

  then the scope: @NamedScope("one") and @NamedScope("two") would be treated as distinct. Previously they were treated as the same scope.
• Legacy implicit assisted injection (not using the @Assisted annotation) is now an error.
• The build will now fail if multiple qualifiers are applied in the same place, instead of picking the first one. This applies both to the new annotation (see below) and javax.inject.Qualifier. A minor exception is you are allowed to have one of each type to aid in migration. In that case the me.tatarka.inject one will be chosen.

Added

• Added a me.tatarka.inject.annotations.Qualifier annotation as an alternative to using typealias. For example, you could do:

  @Qualifier
  annotation class Named(val value: String) 
  @​Inject
  class MyClass(@​Named("one") val one: String, @​Named("two") val two: String)
  @​Component
  abstract class MyComponent {
  abstract val myClass: MyClass
  @​Provides @​Named("one")
  fun provideOne(): String = "one"
  @​Provides @​Named("two")
  fun provideTwo(): String = "two"
  }
  

  This behaves the same as javax.inject.Qualifier does when you have me.tatarka.inject.enableJavaxAnnotations=true.
• Added a new @KmpComponentCreate annotation for nicer multiplatform support. This allows you to create component instances from common code when generating platform-specific outputs.

  // src/commonMain
  @Component
  abstract class MyKmpComponent
  

... (truncated)

Commits

• a6377f8 Bump version for release
• 3d4d374 remove erroneous @​KmpComponentCreator annotation
• 56aa199 bump version for dev
• 9a91124 prepare release 0.7.0
• 068af05 Allows annotating types with a qualifier
• 701021a fix generated code for scoped lazy circular dependency (#313)
• 6fd78d2 Don't reuse symbols between rounds (#393)
• 8a67444 Use stable nodejs v22
• 3f812c4 Update the generated filename for KmpComponentCreate functions (#385)
• 4c64d32 Add a new annotation to generate Component accessors for KMP targets (#370)
• 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 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)

[vganin]

@dependabot merge