-
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
Various cleanup on EA breakout feature branch #1251
Conversation
✅ Deploy Preview for veda-ui ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
… have externallinkbadge hotfix changes
@dzole0311 I had to resolve a good amount of conflicts in the original Feature branch |
LinkProperties are sprinkled in many places prop drilled quite deep, also the work around to support instances since they use the card component is just not ideal, we should probably update their code to pass in linkProps.. but I think we should spend more time looking at the navigation more holistically sometime in the future... |
app/scripts/components/common/map/controls/aoi/custom-aoi-control.tsx
Outdated
Show resolved
Hide resolved
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.
🙇 thanks for doing the extra work.
Adding my 2 cents to LinkProperties: Now that I think, what we should have done is instead of pathAttributeKeyName
, we should have just made LinkElementProps
and make it take whatever props that the component requires since we can't really predict what kind of props that LinkElement will need. 🤔 We can def separate the issue but what do you think?
--- a few hours later ---
Ah, I realized that even if we have LinkElementProps, it can't really replace what pathAttributeKeyName
does since the LinkElement level doesn't know the path yet 😞
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.
- Hiding the external badge works as on prod ✅ Found a minor, non-urgent issue which I will address in another PR
- Tested card functionality and everything worked as expected ✅ The only change I noticed is that the cursor no longer shows as a "pointer" when hovering over E&A Catalog Cards due to the empty link props (which seems appropriate for this case)
I also did some manual testing and couldn't find any issues with this pr/preview link. looks good to me ✅ |
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.
🙇 Thanks for working on this!
### 🚀 Improvements * Exploration & Analysis core VEDA feature breakout #1251 #1154 * Introduce `EnvConfigProvider` to simplify the injection of environment variables from host applications like Next.js #1253 * Remove React Router's `useNavigate` dependency for simplifying the routing #1270 ### 🐛 Fixes * Fix an issue where card images fail to maintain the correct aspect ratio #1265
Related Ticket: #1154
Description of Changes
onClick
fromLinkProperties
Card
Component instead of link propsNote
Built
v5.9.1-ea.0
off of these changesUpdate: Bulit
v5.9.1-ea.1
has been builtValidation / Testing
NextJs Preview with updated version: developmentseed/next-veda-ui#4