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

fix: validate entity type for an urn #1958

Merged
merged 1 commit into from
Oct 23, 2020

Conversation

jywadhwani
Copy link
Contributor

There is no consistent way of validating the type of an urn. This changes attempts to fix it.

Checklist

  • The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
  • Links to related issues (if applicable)
  • Tests for the changes have been added/updated (if applicable)
  • Docs related to the changes have been added/updated (if applicable)

Copy link
Contributor

@mars-lan mars-lan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Drop the changes to datahub-web/yarn.lock?

@jywadhwani
Copy link
Contributor Author

Drop the changes to datahub-web/yarn.lock?

Done

@mars-lan mars-lan added the hacktoberfest-accepted Acceptance for hacktoberfest https://hacktoberfest.com/participation/ label Oct 23, 2020
@jywadhwani jywadhwani merged commit 127d84e into datahub-project:master Oct 23, 2020
@jplaisted
Copy link
Contributor

Hey this just blocked us from moving to the new repo. Can we revert this and make the change there instead?

@mars-lan
Copy link
Contributor

Yeah we can roll this back and cherrypick the change to datahub-gma

jplaisted pushed a commit that referenced this pull request Oct 23, 2020
This change should've been made in datahub-gma instead.

This reverts commit 127d84e.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hacktoberfest-accepted Acceptance for hacktoberfest https://hacktoberfest.com/participation/
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants