-
Notifications
You must be signed in to change notification settings - Fork 6
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
chore: Remove linkProperties from DataCatalog Component #1310
Conversation
…prop, remove unused overline prop from catalog-card
✅ Deploy Preview for veda-ui ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@hanbyul-here i wouldn't really classify this as a |
|
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.
Tested the routing & selecting for the Catalog cards, it works as expected. Also confirming the overline prop isn't needed for the selectable (horizontal-info
) catalog cards.
Related Ticket: #1108
Related PR: developmentseed/next-veda-ui#25
v5.11.3-alpha.0 published from this branch
Description of Changes
As part of the greater holistic approach - I think its best to move away from having our library components tightly integrated w/ routing. This is the first iteration to remove linkProperties. This PR only worries about removing linkProps the DataCatalog Component. DataCatalog view no longer has to pass in linkProperties or have to directly worry about routing, we can just pass in a callback now that decides what to do during some action.
This is an iterative approach, i've created tickets to remove routing from the other core components. But we can't remove routing directly from the Card component itself easily as GHG uses the card component directly here. So that should be its own separate ticket BUT... we are to be redoing the card component for the new instances - where its probably best to rewrite it. As currently its not in an ideal place to scale... so i'll create a placeholder ticket for card component for now but we can probably tackle removing routing when rewriting the card component.
cc @vgeorge @hanbyul-here @dzole0311
Follow-up tickets created:
Notes & Questions About Changes
{Add additonal notes and outstanding questions here related to changes in this pull request}
Validation / Testing