Skip to content
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

Expose ResolveAll for usage as a library #471

Open
Resonance1584 opened this issue Apr 10, 2024 · 1 comment
Open

Expose ResolveAll for usage as a library #471

Resonance1584 opened this issue Apr 10, 2024 · 1 comment

Comments

@Resonance1584
Copy link

I have a use case where I want to use murmur in golang integration tests within Visual Studio Code. VS Code has an option to set a .env file e.g. go.testEnvFile in settings, but as far as I can tell there isn't a way to run murmur before the test or debug is started from within the ide e.g. when clicking "debug test" above a test function.

If ResolveAll is exposed outside of internal I can call it from within the tests and manually set the env vars to their secrets, would you be open to moving this outside of the internal package?

@christianking-gitlab
Copy link

This is something that I would like as well. I have forked the repo and implemented this, and I will submit a PR for the changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants