Handling colons in extra metadata values #64
samuelallan72
started this conversation in
General
Replies: 1 comment 1 reply
-
@swalladge "I don't know", is my correct answer from me ;-) but some thoughts. The spec really needs spaces in between items, it explicitly says non-whitespace so I think you run a low risk of problems if you choose to use colons in your value (you deserve headaches if using in a key 😝 ) which would technically be non-conforming. No one has shot down your idea so might be worth opening an issue as a proposal to allow. I opened #77 as I personally think keys should not start with a number. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
From the spec:
Why must a value not contain a colon? A colon in the value doesn't appear to introduce ambiguity. For example
label:one:two
can only be parsed as a tag with keylabel
and valueone:two
.How do most tools handle this case? Allow it, raise an error, treat the string as part of the description since it's an invalid tag, or only parse
label:one
as the key:value, and leave:two
in the description?Beta Was this translation helpful? Give feedback.
All reactions