Cli optional fields and metadatum fixes #27
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This doesn't change how the metadata is generated, but allows some modified metadata to still be parsed and processed correctly. This enables people like me not interested in the 'vendor' parts to just get rid of the irrelevant information from the metadata by just editing the generated file manually.
When the context URI is longer than 64 UTF-8 bytes, this produces otherwise an invalid encoding.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📍 Allow some metadata fields to be optional.
This doesn't change how the metadata is generated, but allows some modified metadata to still be parsed and processed correctly. This enables people like me not interested in the 'vendor' parts to just get rid of the irrelevant information from the metadata by just editing the generated file manually.
📍 Fix '@context' value to CBOR transformation.
When the context URI is longer than 64 UTF-8 bytes, this produces otherwise an invalid encoding.