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
first of all, thank you for this awesome plugin! It is really promising for a streamlined, spec-driven development.
I have one problem with the plugin, though.
It expects all API to be prefixed with a "route", which defaults to "/api". However, my spec already contains the "/api" prefix, which makes the mocked API available via "/api/api", which does not correspond to the real path.
I would love if the plugin could use the "route" as some sort of "filter", i.e. only requests under the "/api" route are handled by prism, but they are not prefixed with another "/api".
Would that be possible?
Maybe any hint as to where start looking at the code, maybe I can create a merge request myself?
Greetings from Germany,
Daniel
The text was updated successfully, but these errors were encountered:
Hello there,
first of all, thank you for this awesome plugin! It is really promising for a streamlined, spec-driven development.
I have one problem with the plugin, though.
It expects all API to be prefixed with a "route", which defaults to "/api". However, my spec already contains the "/api" prefix, which makes the mocked API available via "/api/api", which does not correspond to the real path.
I would love if the plugin could use the "route" as some sort of "filter", i.e. only requests under the "/api" route are handled by prism, but they are not prefixed with another "/api".
Would that be possible?
Maybe any hint as to where start looking at the code, maybe I can create a merge request myself?
Greetings from Germany,
Daniel
The text was updated successfully, but these errors were encountered: