Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wildcard extended test - is it correct? #88

Open
PawelCzajkowski opened this issue Apr 2, 2020 · 1 comment
Open

Wildcard extended test - is it correct? #88

PawelCzajkowski opened this issue Apr 2, 2020 · 1 comment

Comments

@PawelCzajkowski
Copy link

Hello!
I am trying to use wildcards. To understand I have executed the test from this repo.
What I have found is that it does not work as it is expected (IMO).

When I put this URL "http://localhost:9001//wildcard-extended/__/foobar" then I get correct response "wildcards-extended".
But when I put "http://localhost:9001//wildcard-extended/1/foobar" then I get "Not Mocked".

Is it correct behavior?
What I have to do to not make copies of the same mock file if I want to have following structure:

foo/1/bar/GET.mock
foo/2/bar/GET.mock
...

@karlludwigweise
Copy link

I found that nesting more than 1 level after a wildcard does not work. Multiple Wildcards don't seem to work either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants