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

New default config file #422

Merged
merged 4 commits into from
Oct 16, 2017

Conversation

pmconrad
Copy link
Contributor

Alternative implementation of PR #415
Looks bigger than it is, check the individual commits for better understanding.

Previously, a newly written config file was ignored.
For the included plugins that didn't matter though, because all config file
options (and their default values) are also CLI options, and CLI defaults
always apply, no matter if a config file exists or not.

Now, a new config file is written with the default option values (if any),
and parsed immediately after that. In other words, the config defaults
are applied again. This does not result in a different outcome, at least
with the included plugins.
@oxarbitrage oxarbitrage self-requested a review October 16, 2017 12:31
Copy link
Member

@oxarbitrage oxarbitrage left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

very nice work. tested it and works perfect, code looks good too. if @xeroc agree we can merge this solution.

@xeroc
Copy link
Member

xeroc commented Oct 16, 2017

Nice solution ... much nicer than anything I could have come up with ..

@oxarbitrage oxarbitrage merged commit 274aaf7 into bitshares:develop Oct 16, 2017
@abitmore abitmore mentioned this pull request Dec 26, 2017
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

Successfully merging this pull request may close these issues.

None yet

3 participants