Skip to content

Support for loading mapping files from 'mappings' folder by default #134

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

Open
hem-verma opened this issue Jun 21, 2024 · 2 comments · May be fixed by #184
Open

Support for loading mapping files from 'mappings' folder by default #134

hem-verma opened this issue Jun 21, 2024 · 2 comments · May be fixed by #184
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@hem-verma
Copy link

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

@hem-verma hem-verma added the enhancement New feature or request label Jun 21, 2024
@oleg-nenashev oleg-nenashev added the good first issue Good for newcomers label Aug 9, 2024
@oleg-nenashev
Copy link
Member

Yes, it would be a good addition

@lhcopetti
Copy link

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() ?)

@lhcopetti lhcopetti linked a pull request Apr 5, 2025 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants