We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be useful to have a per-environment container of responses to re-use in multiple routes.
USE-CASE: 401 response returned by every endpoint of a service if no auth header is provided
ideal Mockoon config:
Same thing would be useful for Rules: USE-CASE: basic params validation shared across several responses, but each response adds specific validation
Ideally this "common rules" implementation would also have the benefit to add some sort of "nested rules":
The text was updated successfully, but these errors were encountered:
I will close this issue as a duplicate of #221 and continue the discussion there.
Sorry, something went wrong.
No branches or pull requests
It would be useful to have a per-environment container of responses to re-use in multiple routes.
USE-CASE:
401 response returned by every endpoint of a service if no auth header is provided
ideal Mockoon config:
Same thing would be useful for Rules:
USE-CASE:
basic params validation shared across several responses, but each response adds specific validation
ideal Mockoon config:
Ideally this "common rules" implementation would also have the benefit to add some sort of "nested rules":
The text was updated successfully, but these errors were encountered: