Add support for explorer links in Address component
- Dominant language
- TypeScript
- Stars
- 853
- Forks
- 662
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 8
Description
Currently the `Address` Snap UI component is used in the interfaces to display addresses and account names.
A requirement from Snaps is that they wrap this component around a `Link` to the explorer page. Yet, the explorer is defined in the extension/mobile app and the Snap is not aware of it. Duplicating this information in the Snap is problematic for maintainability and separation of concerns.
**Requirement**
- Add a `asExplorerLink` boolean to the `Address` component wrapping the component in a Link to the explorer.
- Avoid duplication between Snap and extension/mobile
Contributor guide
Research direction
Start at the Snap UI Address component and trace how explorer information is defined in the extension/mobile app. Add the asExplorerLink behavior without duplicating explorer information in the Snap, and verify that the component links to the configured explorer while preserving normal address display.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100