Analyse and implement validation for REST API endpoints #2061
Labels
feature
New feature
priority: undecided
Undecided priority to be assigned after discussion
under discussion
Requires consideration before a decision is made whether/how to implement
Background
In Enceladus ver 3 we would like to have validations not only on UI but on the service and its endpoints as to allow users to opt-in for a more programmatic (and safe) usage of Enceladus.
Feature
Analyse what endpoints we have in API v3 and what validations might be required and implement the validations.
The text was updated successfully, but these errors were encountered: