Slither result "go to" does not consider column positions
Xenomega opened this issue · 1 comments
Xenomega commented
The current implementation of "go to" for a slither issue will select the affected lines of code, which may select too much information. They should instead take into account the lines + columns to start and end at, such that the result range is accurately reflected.