-
Notifications
You must be signed in to change notification settings - Fork 333
remove global name validation #796
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
base: main
Are you sure you want to change the base?
Conversation
a9e47cd
to
24e7261
Compare
24e7261
to
4e2833b
Compare
a09de84
to
4525d21
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please see comments.
735892a
to
8ee38a2
Compare
Signed-off-by: Julius Hinze <[email protected]>
8ee38a2
to
b107693
Compare
…tion Signed-off-by: Julius Hinze <[email protected]>
b107693
to
5d72c76
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it looks pretty good now, except for the IsValidLegacyMetricName
doc comment referring to NameValidationScheme
.
Fixed! |
obsoleted by #808 |
correction, #808 only removes global validation from the decoder, nowhere else. So this PR is still useful |
This PR removes the global
NameValidationScheme
and changes signatures ofLabelName.IsValid
andIsValidMetricName
to accept an explicitValidationScheme
.