We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, the payload validation logic piles validation for each endpoint in a package, e.g. the validation in the group package.
group
It's somehow risky whenever endpoints are added and removed. (open/closed principle)
It should be improved. Some OOP design patterns might be helpful (e.g. strategy pattern).
The text was updated successfully, but these errors were encountered:
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/IAM-953.
This message was autogenerated
Sorry, something went wrong.
a new set of API will deal with validation in a different manner, v0 API can stick with the current setup and avoid refactoring for the time being
v0
No branches or pull requests
Currently, the payload validation logic piles validation for each endpoint in a package, e.g. the validation in the
group
package.It's somehow risky whenever endpoints are added and removed. (open/closed principle)
It should be improved. Some OOP design patterns might be helpful (e.g. strategy pattern).
The text was updated successfully, but these errors were encountered: