Ameba seems to incorrectly show what the line that needs fixing is about ameba HOT 5 CLOSED

That's not a bug. Due to how the Crystal formatter works, Ameba can only show the error in the scope of the whole file.
Also, this concerns only Lint/Formatting rule.

from ameba.

@Sija maybe we can remove that :1:1 at the end for this specific rule in order to avoid confusion?

from ameba.

@veelenga Since the Ameba's issues are attached to the Location I don't see any clean way to do it.

from ameba.

Oh, well, actually we could show the line(s) with changes, but how would that work?

• Show just the first line changed?
• Show all of the lines changed, each one tagged as Lint/Formatting issue?

from ameba.

My idea is to have a new rule prop, let’s say scope which could be Point | Line | File and which defaults to Point. The formatter rule will override it to File. Then each Ameba’s formatter will properly format the output. What do you think?

However, it may break the flycheck formatter which is used by editors to point to the location.

from ameba.