Please enable JavaScript.
Coggle requires JavaScript to display documents.
Flatten inverse changes - Coggle Diagram
Flatten inverse changes
many-to-one :check:
-
-
crud service changes
- we need not get any inverse fields metadata any further :check:
- The related crud service code should work with the flattened out structure :check:
many-to-many :check:
json/db changes :check:
- If inverse=true, create a many-to-many inverse entry in the inverse model configuration :check:
-
-
test case
- Modify the radix json w.r.t new json changes
- Generate the code. It should generate the exact same code.
- Test creation of many-to-one primary / inverse side
- Test creation of many-to-many primary / inverse side
- Both validation and transformation need to be tested/verified
Further optimization
Since after these changes, a model can impact only its own entity/dto files and not any other side i.e inverse,
we can get rid of any hacky code to handle such scenarios i.e changes are spread across multiple files
Any generic code can be retained to allow further extensibility
:check:
Testing:
- Need to test this with radix as well i.e self referential scenarios
- Need to publish the below modules:
- solid-core
-solid-code-builder
- Need to copy boilerplate code from lm project to solid-core-ui
-
-