objectbox / objectbox/objectbox-java
Entity model per Android flavor
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.6k
- Forks
- 311
- PR merge metrics
- No merged PRs in 30d
Description
There may be scenarios where you would like entity models per flavor.
We do not recommend this in general. There is a downside to having a model per flavor: if you share the app ID among flavors you cannot switch without clearing the app data. This is because diverging schema are not compatible to each other (UIDs differ and potentially also IDs).
Because of this we thought it would be a good idea to have a common entity model across flavors. Even if that means that some entities will be around for no use in some flavors.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how Android flavors and shared entity models are handled in this repository. The issue names no files, tests, entry points, or acceptance criteria; clarify whether per-flavor models are intended and what compatibility behavior would count as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- databases, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100