| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
You could remove the comma to make it not conflict for the pre-commit hook. The purpose now is to make the pre-commit workflow passing. Also, per our convention, we would make the title with chore: ... More details about how we name these is documented in the scikit-package webpage. |
Sorry, something went wrong.
|
@stevenhua0320 Unfortunately, it does not seem to be as simple as removing the comma. I tried moving the multiline string to the final dictionary entry and removing the trailing comma, but Black adds the comma back automatically. I also tried replacing the triple-quoted string with concatenated strings using explicit \n\n, and that still did not get both hooks to agree. At this point, the issue appears to be a formatter interaction rather than just the placement of that comma, so I’m looking for a change that will make both Black and docformatter pass consistently without altering behavior. Perhaps there is a way to fix this in the .yaml |
Sorry, something went wrong.
Two ways you could try:
|
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Updated the pre-commit hook versions according to the recent Slack discussion and applied the resulting formatting/linting changes.
One remaining issue is a formatting conflict between black and docformatter affecting the following files:
In each case, the conflict is the same: black and docformatter repeatedly move the comma following a multiline triple-quoted string, preventing pre-commit from passing.