We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mix credo -v
$ mix credo -v 1.7.10-ref.(HEAD odłączone na origin/master).2e15cdd2
elixir -v
$ elixir -v Erlang/OTP 27 [erts-15.2] [source] [64-bit] [smp:32:32] [ds:32:32:10] [async-threads:1] [jit:ns] Elixir 1.18.0-rc.0 (f00f759) (compiled with Erlang/OTP 27)
Gentoo Linux using desktop/plasma profile for version 23.0 and with kernel version 6.6.41.
desktop/plasma
23.0
6.6.41
I have simply tried to use non-literal as Keyword's value. In my case it's user-defined type with some argument.
Keyword
@type type_name :: Keyword.t(Some.remote(some_arg))
This check should not appear for all Typespec attributes | Module @ Elixir documentation.
Checking (…) source files ... Code Readability ┃ ┃ [R] → Use a pipeline instead of nested function calls. ┃ (…) Please report incorrect results: https://github.com/rrrene/credo/issues Analysis took 0.1 seconds (0.04s to load, 0.1s running 102 checks on (…) files) (…) mods/funs, found 1 code readability issue. Use `mix credo explain` to explain issues, `mix credo --help` for options.
The text was updated successfully, but these errors were encountered:
Thx for reporting! 👍
Sorry, something went wrong.
No branches or pull requests
Environment
mix credo -v
):elixir -v
):What were you trying to do?
I have simply tried to use non-literal as
Keyword
's value. In my case it's user-defined type with some argument.Expected outcome
This check should not appear for all Typespec attributes | Module @ Elixir documentation.
Actual outcome
The text was updated successfully, but these errors were encountered: