Provide validation or enums for Service Level Tiers
See original GitHub issueCurrently all service level tiers, such as database tiers, are all strings.
It is currently very hard to build applications to validate input for these things. Are there plans to introduce enums or validation components which we can use to validate input on?
I’m aware of classes such as DatabaseEditions
but these are not really helping since we need to check each property of these classes instead of having a TryParse
on an enum.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
A good practice to present service level validation errors ...
The choice is typically exceptions vs. error codes (or response codes), but the best practice, at least Bloch's, is to only use exceptions...
Read more >Why would you store an enum in DB?
Create verification code that checks to see that each value in the enumeration is in the corresponding table, and that only those values...
Read more >User Levels, Enums and Policies, oh my! · Laravel Bytes
Using Enums to add a level structure to users, and using Policies to authorize actions based on those user levels.
Read more >Validations for Enum Types
Learn how to build validations for enums using Java custom annotations.
Read more >What you need to know about GraphQL enums
Learn how GraphQL enums can help you build more robust and discoverable ... is to provide validation out of the box on operations...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes, this will be addressed in the coming update.
Awesome, thank you!