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

chore: Remove linkProperties from DataCatalog Component #1310

Merged
merged 7 commits into from
Dec 17, 2024

Conversation

sandrahoang686
Copy link
Collaborator

@sandrahoang686 sandrahoang686 commented Dec 9, 2024

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

  • Validate DataCatalog cards are linking correctly
  • Validate selecting cards in DatasetSelectorModal is working as it should

…prop, remove unused overline prop from catalog-card
Copy link

netlify bot commented Dec 9, 2024

Deploy Preview for veda-ui ready!

Name Link
🔨 Latest commit 7c59dc5
🔍 Latest deploy log https://app.netlify.com/sites/veda-ui/deploys/675fbe190d145c00080fa384
😎 Deploy Preview https://deploy-preview-1310--veda-ui.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@sandrahoang686 sandrahoang686 changed the title Remove linkProperties from card and use callbacks instead for card navigation refactor: Remove linkProperties from card and use callbacks instead for card navigation Dec 9, 2024
@AliceR AliceR added the refactor veda-ui/blob/main/docs/adr/002-application-architecture-for-configurability.md label Dec 11, 2024
@sandrahoang686 sandrahoang686 changed the title refactor: Remove linkProperties from card and use callbacks instead for card navigation refactor: Remove linkProperties from DataCatalog Component Dec 16, 2024
@sandrahoang686
Copy link
Collaborator Author

@hanbyul-here i wouldn't really classify this as a refactor but more so tech-debt or chore but its a little more than a chore.. What do you think is best to classify this as? tech-debt doesn't exist as one of the CI options. Also this isn't breaking for current legacy architecture but is breaking for new architecture / nextJs instance - so should I add the !?

@hanbyul-here
Copy link
Collaborator

chore sounds right for me. + Conventional commit is to make the automatic versioning seamless - so let's not worry too much about if we have a 'right' prefix as long as it will version things properly.

@sandrahoang686 sandrahoang686 changed the title refactor: Remove linkProperties from DataCatalog Component chore: Remove linkProperties from DataCatalog Component Dec 16, 2024
Copy link
Collaborator

@dzole0311 dzole0311 left a 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.

@sandrahoang686 sandrahoang686 merged commit b29de0c into main Dec 17, 2024
12 checks passed
@sandrahoang686 sandrahoang686 deleted the 1108-remove-navigation-from-card branch December 17, 2024 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactor veda-ui/blob/main/docs/adr/002-application-architecture-for-configurability.md
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants