Skip to content

Extend optionst to be typed and use it to replace configt and other custom configuration objects #2194

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
chrisr-diffblue opened this issue May 17, 2018 · 2 comments
Assignees

Comments

@chrisr-diffblue
Copy link
Contributor

Currently we have both optionst and configt (plus a few other even more custom configuration options). Each has benefits - optionst is generic but un-typed, and configt is typed, but not very generic... We should expand optionst so that options are type safe, and then replace any usage of configt or other custom config objects with optionst.

@chrisr-diffblue chrisr-diffblue self-assigned this May 17, 2018
@martin-cs
Copy link
Collaborator

I think optionst and configt are used for different things:

#1521

This is not to say that they /should/ be, just a back link to the last discussion of this.

@chrisr-diffblue
Copy link
Contributor Author

Thanks for the link - I wasn't aware of that, so its very useful extra context.

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