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

Consistent enum type in markdown docs #158

Merged
merged 2 commits into from
Aug 25, 2023

Conversation

obowersa
Copy link
Contributor

Consistent usage of String (enum) across the markdown documents where an enum type is used in the schema.

Changes

Consistent usage of String (enum) across the markdown documents where an enum type is used in the schema. This is in relation to #157

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

Consistent usage of String (enum) across the markdown documents where an enum type is used in the schema.

This is in relation to cdevents#157

Signed-off-by: Owen Bower Adams <[email protected]>
@obowersa obowersa force-pushed the docs-consistent-enum branch from 7d756f4 to b840095 Compare August 25, 2023 11:55
core.md Outdated Show resolved Hide resolved
core.md Outdated Show resolved Hide resolved
Co-authored-by: Emil Bäckmark <[email protected]>
Signed-off-by: Owen Bower Adams <[email protected]>
@obowersa obowersa force-pushed the docs-consistent-enum branch from a673b65 to 6f4e99b Compare August 25, 2023 12:40
@e-backmark-ericsson e-backmark-ericsson merged commit 6c4a279 into cdevents:main Aug 25, 2023
xibz pushed a commit to xibz/spec that referenced this pull request Oct 13, 2023
Consistent usage of String (enum) across the markdown documents where an enum type is used in the schema.

This is in relation to cdevents#157

---------

Signed-off-by: Owen Bower Adams <[email protected]>
Co-authored-by: Emil Bäckmark <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants