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
I am using Miragejs in a Svelte project. Recently, I integrated Google Maps in the project and I could not have it working.
It took me a while to understand that it came from Miragejs blocking the requests. You can check the stackoverflow issue about this.
I understand there is a passthrough option, but I do not think this is a good default behavior as it is counter intuitive.
IMO, by default, Miragejs should not intercept any request except the ones explicitly defined in the routes.
If you don't agree with this, at least please add an option to allow any request to the current domain and to other-origin hosts. At the moment, for other-origin hosts, you need to do it so manually if I understood properly the docs.
The text was updated successfully, but these errors were encountered:
Just found this issue, I hit the same problem on an Ember project using MirageJS and Google Maps. Looks like there were changes last fall on Google's side of things that led to these snags.
I am using Miragejs in a Svelte project. Recently, I integrated Google Maps in the project and I could not have it working.
It took me a while to understand that it came from Miragejs blocking the requests. You can check the stackoverflow issue about this.
I understand there is a
passthrough
option, but I do not think this is a good default behavior as it is counter intuitive.IMO, by default, Miragejs should not intercept any request except the ones explicitly defined in the routes.
If you don't agree with this, at least please add an option to allow any request to the current domain and to other-origin hosts. At the moment, for other-origin hosts, you need to do it so manually if I understood properly the docs.
The text was updated successfully, but these errors were encountered: