You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
because JzodElementEditor does not know what to do when faced with "any" type.
Ideal Solution would be to allow the creation of any js value (literal, array, object...), and infer its type along the way, but keeping the "any" for the EntityDefinition. Can we really be that flexible?
If "any" cannot be reasonably enabled in JzodSchema for EntityDefinitions, what would a "reasonable" solution be?
The text was updated successfully, but these errors were encountered:
There's a catch when using "any" in jzodSchemas for EntityDefinitions.
For example, when editing the "Report" EntityDefinition, we get:
This is due to:
because JzodElementEditor does not know what to do when faced with "any" type.
Ideal Solution would be to allow the creation of any js value (literal, array, object...), and infer its type along the way, but keeping the "any" for the EntityDefinition. Can we really be that flexible?
If "any" cannot be reasonably enabled in JzodSchema for EntityDefinitions, what would a "reasonable" solution be?
The text was updated successfully, but these errors were encountered: