-
Notifications
You must be signed in to change notification settings - Fork 28
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
X-Correlator or x-correlator #191
Comments
Agree - to be considered in #188 |
Agree to align |
Agree to align for me also. |
If no comments in different direction, a PR will be generated this week to align naming to "x-correlator" in design guidelines and also CloudEvent artifact |
Problem description
Guidelines in Commonalities specifies "X-Correlator" but almost all API specs define already "x-correlator"
Expected behavior
Even if header name is case insensitive and both options are interoperable, we should define a common behaviour for coherence, aligned with Guidelines.
As de facto API specs are using "x-correlator", it would be less effort to reflect this in the Guidelines.
It would be convenient to set a new linting rule to check that the header is included in the requests and responses, following the agreed format.
Alternative solution
Adjust all APIs using "x-correlator"
The text was updated successfully, but these errors were encountered: