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
in the process of splitting up an API into public and private components, we want to add a public prefix to the API path, but we'd like it to be optional while we are in the process of changing over. Is that possible with the grape prefix keyword? e.g.
prefix:public,optional: true
The text was updated successfully, but these errors were encountered:
That sounds like a great idea - it certainly leaves the original paths intact. However I'm not seeing the same endpoints available with a public/ prefix ... maybe something else in our app ...
I've managed to get it working with:
mountMyAPI=>'/public/myapi'mountMyAPI=>'/myapi'
not sure why the namespace didn't seem to work for us - maybe because we're using these named paths ...?
I'll close this since that's definitely a solution, but if you have time maybe write a spec and reopen if my suggestion doesn't work, that would be a bug.
in the process of splitting up an API into public and private components, we want to add a
public
prefix to the API path, but we'd like it to be optional while we are in the process of changing over. Is that possible with the grapeprefix
keyword? e.g.The text was updated successfully, but these errors were encountered: