-
-
Notifications
You must be signed in to change notification settings - Fork 872
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
Implement option --display-config (Issue #100) #292
Conversation
abraunegg
commented
Dec 18, 2018
- Implement --display-config to show the application configuration without actually performing a sync or application init
* Implement --display-config to show the application configuration without actually performing a sync or application init
Output when run:
Testing of CLI switches:
|
* Update readme & manpage
* Update output to include config option 'drive_id' if configured in the config file when users are attempting to sync from a sharepoint shared library
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The config crash needs fixing, the rest is fine, but see my comment. Thanks for implementing this!
* Fix drive_id config check
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, compile and run tested here.
Are there any further options / config options we should print out when this flag is used?
Thoughts? |
Since this is an exclusive option and not pairable with OTOH, it might be worth haveing |
I agree - potentially beneficial when running the application as well, rather than exit & be able to use / display at the start before running. Would help with future diagnostic situations as well. This issue (#293) also highlights another 'hidden' problem - that is, invalid 'config' options due to spelling or otherwise. Potentially need to add in to always check the 'config' file if present to ensure that all options that are contained within the file are:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be even better solution to parse config into JSON format, and give ability to use this output as config source for "semi-automatic" setup with --use-config='file.json'
It then could be used as debug data file (when submitting issue) and would be easy to validate with JSON schema
I sent a pull request concerning the validation of config file, and I will look into the JSON stuff. Let us discuss this in a different issue. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |