-
Notifications
You must be signed in to change notification settings - Fork 398
New issue
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
clarity on x-extensible-enum usage for events #807
Conversation
When I think about it, the For the event consumers, in turn, it only signifies the list of currently most commonly found values, but does not restrict the future or the past set of possible values in any way. In that regard it's not much different from a free-form string with |
Co-authored-by: a1exsh <a1exsh@users.noreply.github.com>
👍 |
1 similar comment
👍 |
@tfrauenstein wanted to extend the PR as discussed in the Meeting (internal link) |
As discussed in the API Guild meeting ([internal link](https://docs.google.com/document/d/1NahSuMC0LRwFTTrln2m0iDLq0nHzGmF59Gv7xBhKPfQ/edit#bookmark=id.h23t4po7q2os))
done |
Co-authored-by: Tronje Krop <tronje.krop@zalando.de>
Co-authored-by: Tronje Krop <tronje.krop@zalando.de>
👍 |
1 similar comment
👍 |
No description provided.