Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add rule for extensible enums
See original GitHub issueIf enum is used for a field a should rule violation should be fired because we recommend usage of x-extensible-enum, see http://zalando.github.io/restful-api-guidelines/compatibility/Compatibility.html (“Should: Used Open-Ended List of Values (x-extensible-enum) Instead of Enumerations”)
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Developers - Add rule for extensible enums - - Bountysource
If enum is used for a field a should rule violation should be fired because we recommend usage of x-extensible-enum ...
Read more >Extensible Enums - Business Central - Microsoft Learn
Enums can be extended in order to add more values to the enumeration list in which case the Extensible property must be set...
Read more >java - Can enums be subclassed to add new elements?
The recommended solution to this is the extensible enum pattern. This involves creating an interface and using that where you currently use the...
Read more >Extensible Enumerations A Guide for Preparers - FASB
The purpose of this Guide is to explain an XBRL design feature(1), known as extensible enumerations, denoted in the Taxonomy as an element ......
Read more >Extensible Enums in Dynamics 365 Business Central
Three scenarios spring to mind where extending an enum could be particularly useful. Adding On-premise Support. As a rule we try to write...
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
Possibly this could be restricted to objects used for server → client communication (assuming the server is the API owner)? For client → server, enum is fine (and extensible).
@netme
(from Swagger Specs)
I’m working on it.