Skip to content

Releases

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 18 Nov 13:55
721f3ab

What's Changed

  • unused-import: every name a file imports is used in it; # noqa; 0.4.0 by @winding-lines in #8

Full Changelog: v0.3.1...v0.4.0

v0.3.1

Choose a tag to compare

@github-actions github-actions released this 16 Nov 17:58
78c0be0

Moving to 0.3.1

This version adds a new rule, mojo-build-per-test, to the tests group. Like the rest of that group, it is deny by default. It reports a pixi task, CI step or script that runs mojo build on more than 3 test files. Wrappers that pass their arguments on to mojo build count too, such as a compile() shell function or scripts/mojo-build.sh. Building several programs is not reported, only test files.

A project that builds each test file into its own binary will now fail its customs job. In the change that moves the pin, either build the tests once, or set the rule to warn in pixi.toml:

[tool.customs.lints]
# Why it stays as it is.
mojo-build-per-test = "warn"

Its threshold is mojo-build-per-test-threshold (default 3) under [tool.customs].

Also in this version:

  • A test file, for both per-test rules, must now contain a def test_ at its top level when the file exists. Programs under tests/, such as drivers or files that must fail to compile, are not counted.
  • A task that calls something already reported is still reported for the test files it runs or builds itself.

What's Changed

  • mojo-build-per-test: report building more than 3 test files one by one; 0.3.1 by @winding-lines in #7

Full Changelog: v0.3.0...v0.3.1

v0.3.0

Choose a tag to compare

@github-actions github-actions released this 16 Nov 16:36
17d804c

Moving to 0.3.0

This version adds a tests group of two rules, and they are deny by default:

  • functions-in-imported-module (#4): reports an import of a file that calls __functions_in_module().
  • mojo-run-per-test (#5): reports a pixi task, CI step or script that runs mojo run on more than 3 test files.

A project whose tests run with mojo run per file will now fail its customs job. In the change that moves the pin, either build the tests once, or set the rule to warn in pixi.toml:

[tool.customs.lints]
# Why it stays as it is.
mojo-run-per-test = "warn"

Also new: the [tool.customs] configuration (levels allow/warn/deny per rule or group, and mojo-run-per-test-threshold), the -A/-W/-D NAME flags, and the rule's name at the end of each finding. Without a configuration, the import rules behave as in 0.2.1. See the README.

What's Changed

  • The tests group: functions-in-imported-module and mojo-run-per-test, [tool.customs] configuration, 0.3.0 by @winding-lines in #6

Full Changelog: v0.2.1...v0.3.0

v0.2.1

Choose a tag to compare

@github-actions github-actions released this 15 Nov 22:47
7e5c619

What's Changed

Full Changelog: v0.2.0...v0.2.1

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 15 Nov 17:14
0cf2f83

What's Changed

  • A module only inside packages, and a GitHub Action (0.2.0) by @winding-lines in #1

New Contributors

Full Changelog: v0.1.0...v0.2.0

v0.1.0

Choose a tag to compare

@github-actions github-actions released this 15 Nov 16:53