Skip to content

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

@bingenito

Description

@bingenito

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions