I understand your frustration, but let’s try to be more specific.
"Unable to access value holder for property" for @OneToOne relation with embedded entity · Issue #99 · jmix-projects/jmix-data · GitHub - we are unable to reproduce it, could you provide a scenario?
Lazy loading bug with composition - #2 by krivopustov - we’ll try to fix the issue with Kotlin collections.
As for required fetch plans in editors with nested data containers - I don’t think it’s a problem, but we can probably create a fetch plan automatically if it’s absent in screen XML: Automatically include in fetch plan properties for nested data containers · Issue #416 · jmix-framework/jmix · GitHub
Exception saving an entity in DataContextImpl.mergeCommitted() - #4 by klaus - fixed in upcoming v1.2, along with similar issues on saving complex editors.
We appreciate your feedback, it’s always very valuable. Please send us bugreports and we’ll do our best to improve the framework.