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 propose to add support for loading mapping files from 'mappings' folder by default like It is done for WireMockServer.
When there are multiple tests looking for different mapping file, mappings comes really handy without configuring the WireMockServer. it just works out of the box.
But with WireMockContainer, we have to specify which file to load which adds unnecessary configuration.
References
No response
The text was updated successfully, but these errors were encountered:
Hey @oleg-nenashev , I am looking into ways to contribute to the project and I thought I could give this one a try. Could you give me a brief intro on what you would expect from this one if it still desirable?
As suggested, we could load mappings and files from a directory by default (eg: src/test/resources/wiremock/(mappings, __files)). On that same note, would it also make sense to include a new method to change this default path? Similar to what we have on WireMockServer with --root-dir option (eg: .withRootDir() or withRootDirFromResource() ?)
Proposal
I propose to add support for loading mapping files from 'mappings' folder by default like It is done for WireMockServer.
When there are multiple tests looking for different mapping file, mappings comes really handy without configuring the WireMockServer. it just works out of the box.
But with WireMockContainer, we have to specify which file to load which adds unnecessary configuration.
References
No response
The text was updated successfully, but these errors were encountered: