-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
fix(ingestion): fixes producing some URNs with reserved characters #12772
fix(ingestion): fixes producing some URNs with reserved characters #12772
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅ ✅ All tests successful. No failed tests found. 📢 Thoughts on this report? Let us know! |
…eserved-characters
…eserved-characters
@@ -8,6 +8,9 @@ | |||
MetadataChangeEventClass, | |||
OwnershipClass, | |||
) | |||
from datahub.utilities.urn_encoder import RESERVED_CHARS_EXTENDED | |||
|
|||
_RESERVED_CHARS_STRING = "".join(sorted(list(RESERVED_CHARS_EXTENDED))) |
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.
this can probably just be a hardcoded string. if the expected urns are hardcoded, this should be too.
ultimately as long as something is getting encoded, we know the encode_string call is happening and so we're fine on testing
…eserved-characters
…eserved-characters
Checklist