fix (frontend): Partially fixes lineage issues and dataset API handling #1874
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.
This PR fixes the following issues:
Both of which likely stem from the same root cause: that the datasets response for the open source midtier (datahub-frontend) no longer matches with how we are handling datasets in datahub-web internally. This PR doesn't create a perfect parity between the two but should bring us a little closer to how components are currently consuming dataset data.
Upon testing, it looks like the lineage issue is solved and other components are currently working fine.
Will rely on automated tests with the build for the rest.
Checklist