Replies: 1 comment 2 replies
-
|
Not sure this is the right fix, but it does fix it. In to this: it works. Basically the logic there is if my remaining segment is just any empty string then the app sent me a path with a trailing slash and no more path segments. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Some of our codebase has endpoint references written with a trailing slash such as:
${myApiUrl}/someEndPoint/. This throws off Counterfact because even though I have a file atpaths/someEndPoint.tsthat handles the need, Counterfact is expecting a subpath after the trailing slash. If I update the codebase to remove the trailing slash it works, but I'm trying to get my Counterfact setup to be a drop-in for the API that doesn't require the UX side to make changes just to accommodate Counterfact. Ideas?Beta Was this translation helpful? Give feedback.
All reactions