Added document logging & unit tests · ISISComputingGroup/ibex_bluesky_core@0ea446f

src/ibex_bluesky_core/callbacks/document_logger.py#L11

src/ibex_bluesky_core/callbacks/document_logger.py:11:5: D200 One-line docstring should fit on one line

src/ibex_bluesky_core/callbacks/document_logger.py#L11

src/ibex_bluesky_core/callbacks/document_logger.py:11:5: D212 Multi-line docstring summary should start at the first line

src/ibex_bluesky_core/callbacks/document_logger.py#L16

src/ibex_bluesky_core/callbacks/document_logger.py:16:9: D200 One-line docstring should fit on one line

src/ibex_bluesky_core/callbacks/document_logger.py#L16

src/ibex_bluesky_core/callbacks/document_logger.py:16:9: D202 No blank lines allowed after function docstring (found 1)

src/ibex_bluesky_core/callbacks/document_logger.py#L16

src/ibex_bluesky_core/callbacks/document_logger.py:16:9: D212 Multi-line docstring summary should start at the first line

src/ibex_bluesky_core/callbacks/document_logger.py#L16

src/ibex_bluesky_core/callbacks/document_logger.py:16:9: D401 First line of docstring should be in imperative mood: "Initialises current_start_document and filename."

src/ibex_bluesky_core/callbacks/document_logger.py#L24

src/ibex_bluesky_core/callbacks/document_logger.py:24:9: D202 No blank lines allowed after function docstring (found 1)

src/ibex_bluesky_core/callbacks/document_logger.py#L24

src/ibex_bluesky_core/callbacks/document_logger.py:24:9: D212 Multi-line docstring summary should start at the first line

src/ibex_bluesky_core/callbacks/document_logger.py#L27

src/ibex_bluesky_core/callbacks/document_logger.py:27:9: D413 Missing blank line after last section ("Args")

Process completed with exit code 123.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Added document logging & unit tests #5

call-linter-workflow / ruff

Added document logging & unit tests #5

Jobs

Run details

Annotations

The logs for this run have expired and are no longer available.

Re-running jobs...