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
I'd like to be able to hide some editor properties when adding a new row. Right now all properties are included, unless the 'display_required_only' config is used at initialization. The problem with this solution is that I have to make properties that are not required in the business logic, required in the code, which creates a risky situation where if I initialize with an incomplete json object, then an error results.
Is there a way to set certain editor properties to be disabled in the Editor Options?
In the meantime I'm overwriting the code to disable certain editor properties with this code:
The actual logic I'm using checks to make sure I'm acting on the right object editor, but the idea is I'm altering the enabled properties with javascript events after the build. A better solution would be if this could be dealt with during the build, where some editor options config could be used by the build code to disable some editors directly. Please let me know if something like this already exists, or if there's a better way to achieve the desired result.
The text was updated successfully, but these errors were encountered:
General information
Expected behavior
I'd like to be able to hide some editor properties when adding a new row. Right now all properties are included, unless the 'display_required_only' config is used at initialization. The problem with this solution is that I have to make properties that are not required in the business logic, required in the code, which creates a risky situation where if I initialize with an incomplete json object, then an error results.
Is there a way to set certain editor properties to be disabled in the Editor Options?
In the meantime I'm overwriting the code to disable certain editor properties with this code:
The actual logic I'm using checks to make sure I'm acting on the right object editor, but the idea is I'm altering the enabled properties with javascript events after the build. A better solution would be if this could be dealt with during the build, where some editor options config could be used by the build code to disable some editors directly. Please let me know if something like this already exists, or if there's a better way to achieve the desired result.
The text was updated successfully, but these errors were encountered: