Ianleeclark / Paseto

An Elixir implementation of Paseto (Platform-Agnostic Security Tokens)
Other
95 stars 8 forks source link

Bump credo from 1.4.1 to 1.5.0 #39

Closed dependabot-preview[bot] closed 3 years ago

dependabot-preview[bot] commented 3 years ago

Bumps credo from 1.4.1 to 1.5.0.

Changelog

Sourced from credo's changelog.

1.5.0

  • Credo now requires Elixir 1.7 or newer

  • Refactor check runner (much faster now for common scenarios)

  • Add param allow_acronyms to check Credo.Check.Readability.FunctionNames

  • Add name of check to message when printing issues with --verbose

  • Add support for "dynamic" tagging for checks via .credo.exs

    # Overwrite all tags for `FooCheck`
    {FooCheck, [tags: [:my_tag]]}
    

    Add tags for FooCheck

    {SomeCredoCheck, [tags: [:initial, :my_tag]]}

    Tags can then be used as usual, via the CLI switch --checks-with[out]-tag:

    # Only run checks tagged `:my_tag` during analysis
    $ mix credo --checks-with-tag my_tag
    

    Exclude all checks tagged :my_tag from analysis

    $ mix credo --checks-without-tag my_tag

New switch to enable file watcher

You can now ask Credo to re-run on file changes:

  $ mix credo --watch

New diff command

You can now ask Credo to only report changes in files that were changed since a given Git ref:

  $ mix credo diff HEAD^
  $ mix credo diff master

You can, of course, combine this with the new --watch switch to iteratively fix issues that have come up since the last release:

  $ mix credo diff v1.4.0 --watch

New general check param :files

You can now include/exclude specific files or patterns for specific checks.

The syntax is the same as for the top-level :files key:

# check included for Elixir files in lib/ only
{Credo.Check.Consistency.ExceptionNames, files: %{included: ["lib/**/*.ex"]}},

check excluded for a specific file

</tr></table> ... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)