-
Notifications
You must be signed in to change notification settings - Fork 11
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
Format JSON file contents to allow for easier editing #525
Conversation
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 for submitting changes.
I'd guard this feature behind some configuration so the change of storage has no impact without explicitly requesting so.
This could be done by adding a facultative option object in the Config constructor.
It could then be used in the decorator to run the sync function with the expected behaviour.
Yeah, good idea, I will add that... I am thinking an
Also, do you mind if I add |
Can you split that one in another PR so limit the diff to the corresponding changes? |
@de-luca - would you mind checking this PR now please? I will do a separate one after this with |
Codecov Report
@@ Coverage Diff @@
## master #525 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 3 3
Lines 79 87 +8
Branches 11 16 +5
=========================================
+ Hits 79 87 +8
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
I've removed the redundant |
Thank you for the submission, Good job! |
Currently the JSON file contents are written on a single line. If this external
config.json
needs to be edited externally, it is very hard to do so. This change uses a 2 space tabbed format whenutils.sync
is called to ensure the JSON is formatted in a more friendly, readable & editable format in the file.