You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### Thrown Responses
Note that this does not handle thrown Response instances from your loader/action functions. The intention of this handler is to find bugs in your code which result in unexpected thrown errors. If you are detecting a scenario and throwing a 401/404/etc. Response in your loader/action then it's an expected flow that is handled by your code. If you also wish to log, or send those to an external service, that should be done at the time you throw the response.
so if I understand well, it means that we actually can't setup cors globally, can we ?
I'm trying to build a pwa but I struggle with ssr/clientActions/actions etc.
so my codebase is a bit ugly you might think, but anyway here I am
you must run yarn dev-spa and yarn prisma-setup && yarn dev-serve and have a local postgres running
Expected behavior
no logs from entry.server when called from _accueil.connexion or tableau-de-bord._index
so the cors required for tableau-de-bord are not setup
meaning that I should setup for each route where I return a json
Screenshots or Videos
No response
Platform
OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
On your docs here: https://remix.run/resources/remix-utils
you write:
I did, quite properly I think here
but it wasn't working, and I lost quite a few hairs on it
until I went to Remix's
entry.server
doc here: https://remix.run/docs/en/main/file-conventions/entry.server#thrown-responseswhere it's written
### Thrown Responses Note that this does not handle thrown Response instances from your loader/action functions. The intention of this handler is to find bugs in your code which result in unexpected thrown errors. If you are detecting a scenario and throwing a 401/404/etc. Response in your loader/action then it's an expected flow that is handled by your code. If you also wish to log, or send those to an external service, that should be done at the time you throw the response.
so if I understand well, it means that we actually can't setup cors globally, can we ?
Your Example Website or App
https://github.com/betagouv/zacharie/pull/10/files/b293645c87bb84e8efd7da6363dc14a67242303e#diff-dcc994af97e802c6310510c47d7f6b6253b153032fbe29a65b133c88238a77c6
Steps to Reproduce the Bug or Issue
I'm trying to build a pwa but I struggle with ssr/clientActions/actions etc.
so my codebase is a bit ugly you might think, but anyway here I am
you must run
yarn dev-spa
andyarn prisma-setup && yarn dev-serve
and have a local postgres runningExpected behavior
no logs from
entry.server
when called from_accueil.connexion
ortableau-de-bord._index
so the cors required for
tableau-de-bord
are not setupmeaning that I should setup for each route where I return a
json
Screenshots or Videos
No response
Platform
Additional context
No response
The text was updated successfully, but these errors were encountered: