So when the user goes to a broken non-existing asset url, both those routes run. Each route tries to find the asset and fails and throws an error. Then we see 2 different errors in Sentry and in the terminal, even tho they are related to the same instance.
What is the expected behaviour?
Throw the error just 1 time.
I am wondering if switching to single fetch will resolve this. IMO it should.
Contact Details
No response
What happened?
Steps to reproduce:
So in this flow we have the following routes:
assets.$assetId.tsx
assets.$assetId.overview.tsx
So when the user goes to a broken non-existing asset url, both those routes run. Each route tries to find the asset and fails and throws an error. Then we see 2 different errors in Sentry and in the terminal, even tho they are related to the same instance.
What is the expected behaviour?
Throw the error just 1 time.
I am wondering if switching to single fetch will resolve this. IMO it should.