-
Notifications
You must be signed in to change notification settings - Fork 3
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
Refactor zinolib config parsing #22
Conversation
Codecov Report
@@ Coverage Diff @@
## main #22 +/- ##
==========================================
+ Coverage 67.63% 71.12% +3.48%
==========================================
Files 9 13 +4
Lines 1029 1136 +107
==========================================
+ Hits 696 808 +112
+ Misses 333 328 -5
... and 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
SonarCloud Quality Gate failed. 0 Bugs No Coverage information Catch issues before they fail your Quality Gate with our IDE extension SonarLint |
a6c77fd
to
e92a7be
Compare
b765b6f
to
cea2c4e
Compare
4da65c2
to
b8feaf3
Compare
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.
I was asked to look particularly at the tests, but I could not resist suggesting type annotations to a lot of the code - until I gave up, because there were none at all; I'm sure you can figure out the annotations yourself 😆
I think this config parsing code really is a nice touch, and the tests seem to mostly cover what is needed.
Otherwise, SonarCloud has flagged 4 potential code smells that have some merit, I'm not going to repeat those here.
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.
I think the config parsing code is neatly done. I've created a separate issue for type annotations (and considering adding a techdebt
label ;) )
My only concern is this: The tests don't seem to actually be running in the github workflows. The test results are empty. This is likely not caused by this PR, but should be fixed. I was surprised the tests didn't catch the missing import that @johannaengland pointed out, and now I see why...
Joy. They run locally of course. They run on github actions too, what fails is only the last step. |
- allow storing config file elsewhere than users' home directories - add tests!
9d586d4
to
f140df8
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
They run on github action stoo, what fails is only the last step. |
Closes #11 as a bonus.
The
normalize
-function fixes a bug (placement of globals) inparse_tcl_config
and is in preparation for the new stuff.I would especially like feedback on the tests/file handling in the tests.