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
Describe the solution you'd like
Data provided by users for execution of an action should be encapsulated into OperationData. It should be provided for the certain steps in the custom action, and before it is executed, a validation should be performed. Validators for Parameters are defined in the RDF representation of an action.
Describe alternatives you've considered
A part of validation might be moved in the later phase on client side and performed within JavaScript code (e.g. isNotNull)
Probably an interface might be defined for elements which should be validated (similarly as Removable and derrefence, or RunnableComponent and run). The other option might be to extend RunnableComponent with validate method, which basically will pass through associated validators and invoke isValid method.
Can we introduce notation for definition validation rules or use some existing notation to make list of validators easy for customization by non-Java developers?
Describe the solution you'd like
Data provided by users for execution of an action should be encapsulated into OperationData. It should be provided for the certain steps in the custom action, and before it is executed, a validation should be performed. Validators for Parameters are defined in the RDF representation of an action.
Describe alternatives you've considered
A part of validation might be moved in the later phase on client side and performed within JavaScript code (e.g. isNotNull)
Additional context
https://github.com/litvinovg/Vitro/tree/dynapi/api/src/main/java/edu/cornell/mannlib/vitro/webapp/dynapi/components/validators
The text was updated successfully, but these errors were encountered: