Skip to content
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

Question: Should we require all enums in context types to be camel cased? #1265

Open
Tracked by #1292
bingenito opened this issue Jul 16, 2024 · 0 comments
Open
Tracked by #1292

Comments

@bingenito
Copy link
Member

Question Area

[ ] App Directory
[ ] API
[x] Context Data
[ ] Intents
[ ] Use Cases
[ ] Other

Question

Mix casing in enums can cause problems for serializations in other platforms. Should we add to best practices and review that all new enums defined as fields in context types to be camel cased?

Example: This came up as an issue when adding 2.1 TransactionResult status to fdc3-dotnet. The values are not camel cased.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant