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

Configuration #11

Open
JoranHonig opened this issue Oct 13, 2019 · 7 comments
Open

Configuration #11

JoranHonig opened this issue Oct 13, 2019 · 7 comments

Comments

@JoranHonig
Copy link
Owner

Currently vertigo leverages a range of command line parameters to configure mutation testing runs.
With a decently sized projects one might end up using +10 command line parameters, which is-- not ideal.

To solve this vertigo should be extended with the ability to use configuration files.

Example of what this could look like:

vertigo run -c vertigo.yml

Example configuration:

networks:
    - development 1
@jaymcgrath
Copy link
Contributor

Joran - Thanks for tagging this with the Hacktoberfest label. I'm going to start work on this one.

work plans:
fork the repo
look at how configurations currently work in vertigo
look for existing implementations of configuration yamls in python (or libraries which make this easy)
implement config ymls and tests
🎉

@JoranHonig
Copy link
Owner Author

@jaymcgrath That's super awesome!
Let me know if you have any questions.

@jaymcgrath
Copy link
Contributor

You bet! I'm going to be opening a draft PR soon to track this work, and probably digging into it formally this weekend.

@jaymcgrath
Copy link
Contributor

I've opened a few minor PRs with things I encountered when getting set up. I've been researching ways to implement this, and this click-config library looks promising, although a little outdated:
https://github.com/EverythingMe/click-config

@JoranHonig
Copy link
Owner Author

click-config seems like an in maintained small project. I’d prefer to not add a dependency to their project here 😅

@JoranHonig
Copy link
Owner Author

Maybe manually loading yaml and populate unset variables is the way to go here

@burke-md
Copy link

I see some work had begun on this issue but doesn't seem to have been merged in. Would it be inappropriate to throw my hat into this ring? @JoranHonig,

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

No branches or pull requests

3 participants