objectbox / objectbox/objectbox-java

same property converter names conflict

Open
#1,198 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Java
Stars
4.6k
Forks
311
PR merge metrics
No merged PRs in 30d

Description

Is there an existing issue?
Build info
  • ObjectBox version: [4.0.3]
  • OS: [Android ]
  • Device/ABI/architecture: [arm64-v8a ]
Steps to reproduce

file A.kt:

class A {
     @Convert(converter = B.Converter::class, dbType = String::class)
     var b:B?=null

     @Convert(converter = C.Converter::class, dbType = String::class)
     var c:C?=null
}

class B {
     class Converter...
}

class C {
     class Converter...
}

Expected behavior

generated ACursor.java:

...
import apple.ios.watches.model.B;
import apple.ios.watches.model.C;
...
private final B.Converter bConverter = new B.Converter();
private final C.Converter cConverter = new C.Converter();
...
Actual behavior

generated ACursor.java:

...
import apple.ios.watches.model.B.Converter;
import apple.ios.watches.model.C.Converter;
...
private final Converter bConverter = new Converter();
private final Converter cConverter = new Converter();
...
Code
Code

Logs, stack traces
Logs

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with the Kotlin classes A, B, and C, then inspect the generated ACursor.java and the converter import and field-name generation. Done means both converters retain distinct B.Converter and C.Converter references in the generated Java.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, kotlin
Domain
databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.