We generally output explorer links for users when using the CLI/remote helper, however, if they're not connected then this won't happen because nothing was synced. It might be useful to have a way of outputting the links after the fact, so that people can generate and click them.
Interesting, I think this is something I can look into.
So I'm listing here a few options:
- we could provide the links in
rad patch show - provide a separate crate that loads repo and cob and provides a link based on the
publicExplorerconfig property - a separate command in
rad patchandrad issueand mayberad inspect?
provide a separate crate that loads repo and cob and provides a link based on the publicExplorer config property
I think I like this approach the most. We're also talking about the fact that explorer links can and should be configured up-front in the future, i.e. not default to app.radicle.xyz. Making this a more re-usable component seems to make the most sense to me. It could provide a binary rad explorer for outputting the links. We could then re-use those components in the rad CLI for outputting in rad patch, rad issue, or whatever else.