-
Notifications
You must be signed in to change notification settings - Fork 107
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
Allow users to move mock under a scope #21
Comments
Hey @nicolas-besnard , Nice feature which is already under development :D (issues #7 #8). Each mock will have a namespace with the default one mapping to the root path of the application. Feel free to propose your implementation, you might have thought something better than I have. Thanks a lot! |
Happy to contribute if the code is on a branch :) |
I'll update this issue once I push to the branch (hopefully till the end of next week) Thanks again! |
Any news on that? |
@nicolas-besnard Hey! Sorry for the delay 😒 I've been busy... I've paused the other issues (#7, #8) and I'm not sure about when I'll work on them again (soon though). Go ahead with your proposal and create a pull request once done! Thank you very much and happy new year! |
If I've a lot of mock, it might be nice to be able to prepend the route of all my mocks by something (e.g add
/api/v1
to some mock).I'd love to have a view with all my mocks and drag them to build my desired path.
It might also be interesting to use this feature to create a "common" configuration (e.g. common headers)
If you'd like this feature, I'm happy to propose an implementation.
Cheers :)
The text was updated successfully, but these errors were encountered: