David Kubečka
David Kubečka
Environment: ``` IntelliJ IDEA 2021.1 (Ultimate Edition) Build #IU-211.6693.111, built on April 6, 2021 ``` This is my sample Run Configuration: Then the generated command is (notice the extra comma...
### Description It seems that just having EV implementations generated by the annotation processor breaks some flows, e.g. when an existing entity view is updated with a view that has...
Currently generated `EntityViewImpl` constructors possess two properties that make them unusable for saving the new EV instances: - `$$_isNew` returns false therefore the EV instance can't be saved - the...
Use case: I need to prevent a field to appear in the GraphQL input object type, but still make it appear in the output type. Also, I need the setter...
### Description tl;dr: `entityViewManager.save` wrongly downgrades the actual entity view type to a base type, even when there's proper entity/entity view inheritance set up. This leads to issues e.g. in...
Applying an EntityViewSetting with non-empty `fetches` to a `CriteriaBuilder` instance leads to this error: ``` Specifying fetches for @UpdatableEntityViews is currently disallowed. Remove the fetches! ``` The reason behind this...
Update: Originally there was a different description but through a thorough discussion the goal can now be summarized as: - facilitate Spring Data repository naming conventions while allowing to pass...
For some unknown reason a classMappingIndex sometimes points to a non-present field in the tuple (filtered via fetches mechanism). The correct fix should be somewhere else but that this is...
Although there are a lot of (reasonable) restrictions on creatable EVs, a requirement on the presence of setters for all entity properties is not among them for some reason. That...
I don't have a simple reproducer for this but the situation is roughly following: - EV A contains (possibly deeply nested) a collection of EV B which has `@EntityViewInheritance` defined...