Fix external link badge display for tools hosted under the same domain #1192
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.
Related Ticket: #1187
Description of Changes
After discussing with @hanbyul-here during pod week, we identified two potential solutions:
Option 2 requires less configuration for developers/users of VEDA instances, but it's not easy to test locally especially if we want more fine-grained control over future integration tests. So the implementation here goes for Option 1.
More context: https://developmentseed.slack.com/archives/C063GD0NYP8/p1728407361439379
isLinkExternal
prop that can be passed to the story as a configurationhttp/https (/^https?:\/\//)
remains in place as a fallback if the new prop is not presentNotes & Questions About Changes
Validation / Testing
isLinkExternal
prop in some of the stories and validate that it shows/hides the "External Link" badge in the UIisLinkExternal
prop that you added and see if the UI still behaves as expected (e.g if the link you added in the story .mdx file hashttps
, it will be marked asExternal Link
in the UI cards)