chore: update pre-commit#184
Conversation
|
@danielsirakov same here. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #184 +/- ##
=======================================
Coverage 71.63% 71.63%
=======================================
Files 25 25
Lines 3437 3437
=======================================
Hits 2462 2462
Misses 975 975
🚀 New features to boost your workflow:
|
|
For some weird reason this is deleting blank lines after the docstring. I asked claude and it seems as if this is a bug in v1.7.8 of docformatter which people have requested fixes for. Please could you try again (let's close this PR so we don't merge all the back and forth history) pinning to 1.7.7 and see what happens? |
|
@danielsirakov could you revisit this one as we have an agreement that deleting line form |
|
The files look Ok. We just need to check if this version is passing pre-commit |
|
@danielsirakov Could you take a look for the failure of |
Sounds good, I'll take a look after I make the last few edits to diffpy.structure |
…rfit into update_pre-commit # Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
|
I was able to bypass the docformatter and black conflict by changing triple quotes to just using double quotes in 3 files. Let me know if this is an appropriate workaround. @stevenhua0320, ready to review |
|
@danielsirakov I think we have one left for the conflict here: |
I think this had something to do with me merging my edits with the bot edits; I just ran the pre-commit, and it edited the file automatically and passed once I ran it again. I'll push again with the pre-commit's edit. |
|
@stevenhua ready to review |
|
@danielsirakov Still not passing, first you could do the |
Sorry about that, it said it was passing when I ran the pre-commit before pushing so I’m not sure why that’s happening. I’m not home right now, but I’ll take a look as soon as I’m back. |
sbillinge
left a comment
There was a problem hiding this comment.
I left comments. Let's try moving the failing module level docstrings to the top
| Exceptions used for SrFit - specific errors. | ||
| """ | ||
|
|
||
| "Exceptions used for SrFit - specific errors." |
There was a problem hiding this comment.
This one should be a docstring I think. Does it work putting it right at the top of the file but with triple quotes?
| # | ||
| ############################################################################## | ||
| """Universal import functions for volatile SasView/SansViews API-s.""" | ||
| "Universal import functions for volatile SasView/SansViews API-s." |
There was a problem hiding this comment.
This should be a docstring, try moving to the top
| # | ||
| ############################################################################## | ||
| """Functions for binding arguments of callable objects.""" | ||
| "Functions for binding arguments of callable objects." |
@stevenhua0320, ready to review