Add Sentry config and ErrorBoundary Component#1528
Conversation
|
CLA Assistant Lite All Contributors have signed the CLA. |
ESLint Summary View Full Report
Report generated by eslint-plus-action |
|
Travis automatic deployment: |
|
Travis automatic deployment: |
|
Travis automatic deployment: |
|
Travis automatic deployment: |
|
Travis automatic deployment: |
|
Travis automatic deployment: |
| <Button | ||
| size="md" | ||
| color="primary" | ||
| onClick={() => { | ||
| window.location.href = '/app/' | ||
| }} | ||
| > | ||
| Go to Landing | ||
| </Button> |
There was a problem hiding this comment.
right, we should add a Link component in Components. And make it possible to look like a button.
There was a problem hiding this comment.
@mikheevm do you know if we already have a link with the styles of a button in Gnosis? otherwise, I would leave it as it is and create a ticket in Components
There was a problem hiding this comment.
Ticket created 5afe/safe-react-components#72.
There was a problem hiding this comment.
@mikheevm I just started the ticket to add the Link component, but, should we use links as buttons? Technically we could, we only need to "copy" all the material-ui styles for the button and apply them to the anchor element. But does it make sense? shouldn't we use the links with a different style than buttons? they are used for different actions so it's reasonable they should use different styles.
What I'm suggesting is that we should change the button and use the link style, like in here:

There was a problem hiding this comment.
There was a problem hiding this comment.
TLTR, I think we should separate the actions from navigation, meaning, if we want to move inside the page or to another page, we should use links with link styles. If we want to trigger an action, we should use buttons with button styles.
Giving a quick review of the app the only inconsistency I found was in the nav of each section:


It should have the button style.
|
Travis automatic deployment: |
|
Travis automatic deployment: |
|
Travis automatic deployment: |
|
Travis automatic deployment: |
|
Travis automatic deployment: |
|
@nicosampler, I think that the case for when we know the address and redirect to the /balances page is not working. See #1289 (comment) This invalid URL redirects to https://pr1528--safereact.review.gnosisdev.com/rinkeby/app/, given that the safe address is valid |
|
@fernandomg pushed the fix, can you check it now, please? |
|
Travis automatic deployment: |
@nicosampler It works fine. Something I want to understand, as I interpreted the requirements a bit differently. I thought that the error page will be shown, and when clicking 'go home' it would redirect to By "known safe" I understood something around querying the tx-service ( If the service does not recognize the Safe, we redirect to That way, if I enter an EOA or any address, it will prevent loading the Safe App if it's not a known Safe Address for the current environment. |
@fernandomg I think we never talked about that flow but seems an interesting idea. The idea of this ticket was:
I think we should create a ticket for the flow you are proposing |
|
Travis automatic deployment: |
Closes #1289.