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
I have searched existing issues to ensure a similar issue has not already been created
Description
We often have scenarios where our mocked HTTP responses are quite extensive, making our Mockaco configuration JSON files long and harder to manage. To enhance readability and maintainability, we'd like to propose a feature that allows external JSON file references within the mock files.
Proposed solution
It would be beneficial to have a syntax or mechanism in the mock configurations that can specify an external JSON file to be read and inlined during the mock's runtime. For example:
Enhance the Global object to allow users to define and set values that persist throughout the lifecycle of the Mockaco service. This would enable setting large common response structures or data once and then reference them in multiple mock endpoints.
For example:
<#
Global["some-data"]={name: 'Bob'}
#>
Additional context
No response
The text was updated successfully, but these errors were encountered:
Prerequisites
Description
We often have scenarios where our mocked HTTP responses are quite extensive, making our Mockaco configuration JSON files long and harder to manage. To enhance readability and maintainability, we'd like to propose a feature that allows external JSON file references within the mock files.
Proposed solution
It would be beneficial to have a syntax or mechanism in the mock configurations that can specify an external JSON file to be read and inlined during the mock's runtime. For example:
Alternatives
Enhance the Global object to allow users to define and set values that persist throughout the lifecycle of the Mockaco service. This would enable setting large common response structures or data once and then reference them in multiple mock endpoints.
For example:
Additional context
No response
The text was updated successfully, but these errors were encountered: