You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When having multiple function calls and arguments, it is hard to tell which one is bringing up the issue.
As of now, i need to read the docs for both functions involved in that line to see which one is the one the message refers to
.
It will be nice if the message would say:
lib/ex_doc/language/elixir.ex: The function call Atom.to_charlist/1 line 95 is expected to have type nonempty_list(A) as its argument, but it has type string()
If the function has more than one argument it should read "as its 2nd argument"
The text was updated successfully, but these errors were encountered:
That would be a good enhancement, indeed 👍 Otherwise, I think the relevant part of the expression could be underlined/highlighted to make it unambiguous which part is expected to have the mentioned type.
When having multiple function calls and arguments, it is hard to tell which one is bringing up the issue.
As of now, i need to read the docs for both functions involved in that line to see which one is the one the message refers to
.
It will be nice if the message would say:
lib/ex_doc/language/elixir.ex: The function call Atom.to_charlist/1 line 95 is expected to have type nonempty_list(A) as its argument, but it has type string()
If the function has more than one argument it should read "as its 2nd argument"
The text was updated successfully, but these errors were encountered: