-
Task
-
Resolution: Unresolved
-
Normal
-
None
-
None
Some hard-coded Flow.js type definitions (MergeableEntityT, MergeableEntityTypeT, TaggableEntityT, TaggableEntityTypeT...) are mapping the corresponding properties in the file "entities.json" (now generated from "entities.mjs"). It violates the MVC pattern as the code under "root" is supposed to implement the view rather than define the model. Also it mistakenly allows Flow types to mismatch properties defined in "entities.json" and used by the back-end.
A solution would be to write a script that generates the needed Flow types from "entities.mjs" and a mapping from property names to needed Flow type names.
- is related to
-
MBS-12552 Define usage of the term “entity type”
- Review Submitted