Issues filed for rrrene/credo

View Full Project
Do you use credo? Leave a review!

Rate of open issues in the last 60 days

credo open issues (View Closed Issues)
  • over 1 year Credo should not complain about ParenthesesInCondition in one-line `if` call
  • over 1 year Proposal: prefer implicit try in functions
  • over 1 year Credo crashes with httpc error when starting
  • over 1 year Suggestion: NeverPipeOnce
  • over 1 year Restrict to only functions of the same name and zero arity
  • over 1 year Proposal: Add `--no-color` to prevent ANSI coloring of output
  • over 1 year Bug: get warning about operation evaluating to 0 when operation doesnt equal 0.
  • over 1 year False positive consistency warning
  • over 1 year Setting `strict` from Config instead of CLI
  • over 1 year Bug: Large Number Readability for two large floats on one line crashes credo
  • over 1 year Proposal: New rule - Missing @spec and @doc rule for functions
  • over 1 year Proposal: plugins for library-specific checks & analysis
  • over 1 year SpaceAroundOperator Rule does not trigger when expressions are not assigned to a variable
  • over 1 year Better support in umbrella projects
  • over 1 year Not possible to turn of Alias
  • over 1 year Inline @lint has strange behavior depending on code after it
  • over 1 year Consistency check: let SpaceInParenthesis allow empty params without space
  • over 1 year Ability to ignore length of @typedoc (or any @*doc) to support wide markdown tables
  • over 1 year Check all public functions have @doc
  • over 1 year Multi alias/import/require/use recommendation
  • over 1 year - in macros are treated as operations
  • almost 2 years @lint attribute does not work for functions defined inside a quote
  • almost 2 years Implement the ignore_strings option for line length checks
  • almost 2 years Consistency Check Idea: Pattern-match assignment on the left vs right
  • almost 2 years @lint {Credo.Check.Design.DuplicatedCode, false} doesn't work on ExUnit setup blocks
  • almost 2 years exclude whole modules ?
  • almost 2 years Credo runs really slowly on my project
  • about 2 years Is "Case statements should not only contain `true` and `false`." a good default?
  • about 2 years Question: Is there a way to force 2 spaces?
  • over 2 years Warn when module contains function of same name but different arity of behaviour callback
  • over 2 years Project Roadmap
  • over 2 years Persistent handling of issues

credo closed issues

  • over 1 year Suggestion: Do not check for @moduledoc and @doc if the extension is .exs
  • over 1 year mix credo raises (FunctionClauseError) no function clause matching in Regex.match?/2
  • over 1 year Bug: Credo missing hex function after upgrading to latest versions
  • over 1 year Cannot run credo mix task
  • over 1 year Credo crashes with hex 0.14.0 due to using Hex.Utils.ensure_registry!/0
  • over 1 year Non alphanumeric variable names
  • over 1 year Default .credo.exs file from library always loaded / used?
  • over 1 year Bug in regex
  • over 1 year Repo Issue Organization Proposal/Discussion
  • over 1 year Bug in NameRedeclarationByDef
  • over 1 year Double negative
  • over 1 year Incorrect warning when using pipe in capture.
  • over 1 year @lint rule exception does not disable checks on constants
  • over 1 year function_name used for Stream.repeatedly includes argument
  • over 1 year Mix claims there is a new version of credo but tagged code finishes at 0.4.10
  • over 1 year Failing ABC test on simple but large map
  • over 1 year not all long lines are reported
  • over 1 year is there a way to specify `strict` in a config?
  • over 1 year Don't print "showing priority issues" if there are no issues
  • over 1 year Don't enforce @moduledoc requirement modules declared within Test modules
  • over 1 year False positive with grouped logic in if statement
  • over 1 year If-statements in combination with the pipe operator
  • over 1 year Credo 0.4.9 ignore excluded files
  • over 1 year Credo 0.4.9 blows up with a list of excluded files.
  • over 1 year Is there a way to use credo with syntastic?
  • over 1 year `no function clause matching in Credo.Sources.find/1` error
  • over 1 year Large numbers should be written with underscores
  • over 1 year Cond Statements