Releases: nevinera/quiet_quality
Releases · nevinera/quiet_quality
1.5.1
Release 1.5.1
- Refactor ConfigParser to just parse the config into ParsedOptions, separating
the file-filter/excludes handling properly (#114) - Update the standard/rubocop constraints (dev-only)
- Fail the pipeline when rspec encounters non-spec failures (#120 resolves #119)
- Expose error messages when brakeman encounters errors (#122 resolves #115)
1.5.0
Release 1.5.0
- Update to comply with current standardrb rules, and use checkout@v4
- Add a
-X/--exec
argument that allows you to let qq craft the command, but
then actually exec the command instead of running it and handling its output.
Especially useful for things likerspec
, where the output it gives you about
failing tests is very useful, and qq is mostly only helpful for determining
what specs to run. - Add a
--message-format
argument andmessage_format
config file option,
which allow for a fairly complex configuration of the output format for
messages, so they can be displayed in various colorized/tabular formats.
1.4.0
1.3.1
1.3.0
- Support (and enable by default) colorizing the console stderr output from
bin/qq
- disable with the--no-colorize
flag or thecolorize: false
configuration entry. (#94, resolved #36) - Introduce a Logging facility, and add the
--verbose/-v
flag - supply it
either once or twice to enable (colorized) logging in eitherinfo
ordebug
level, providing much more detail about what's going on during execution.
1.2.2
- Add some code to the Rspec::Parser that cleans the json of certain text that
simplecov may write into the rspec json output. (#91, resolves #86) - Include the name of the originating tool in the printed message, and the
annotation, when a warning is presented. (#90 resolves #72) - Support
normal
as a logging level, and the--normal
and-n
cli
arguments. This is the default value, so this really only matters if your
config file sets another value and you want to override it from the cli.
(#91, resolves #86)
1.2.1
Release 1.2.1
- Fix the handling of the various ways to specify whether tools should limit
their targets to changed files or run against the entire repository. The
configuration systems had disagreements on what to call the options in
question, which resulted in some configuration entries being ignored. We
enforce a set of validations on reads and writes now to avoid such a problem
in the future (#89, resolves #88) - Add coverage-checking, and then improve test coverage and remove unreferenced
code as a result. (#87)
1.2.0
- Support
--light
,--quiet
, and--logging LEVEL
arguments for less output
(#78, resolves #37) - Support the markdownlint tool
(#79, resolves #58) - Extract BaseRunner (#82) and RelevantRunner (#83) parent classes from the tool
runners, to allow new tools to be more easily implemented. (Resolves #81) - Extract a Cli::Presenter from the Entrypoint, to simplify pending work on cli
presentation (#84, resolves #42) - Update the docs a bit, and add a changelog
1.1.0
- Support
--version/-V
flag on the command-line - Support the
file_filter
per-tool config (in the config-file only), for filtering the appropriate paths for particular tools with a regex - Add more consistent configuration-file keys, to better match the arguments accepted by the command-line. Specifically, support
annotate
alongsideannotator
, and at global and tool level supportall_files
andunfiltered
alongsidechanged_files
andfilter_messages
(with reversed meanings, of course) - When no tool names are supplied on the command-line and no config file exists (or the config file doesn't specify
default_tools
), exit with a failing status and explain, instead of just running all of the tools. That's rarely a useful thing to do anymore.