First of all great tool! 💪🏻
We are aiming to use this just for errors. The most common case for us is when production code is altered but the author is forgetting to refactor unit-tests based on the changes of production code. In that case a non-inlined comment will be posted to PR since the unit-tests have not been altered yet. This comment though contains very little information in regards to where the error is located.
So it would be nice to maybe:
- Include the filename & maybe line/column where the compilation error is located
- Add a hyperlink to the above so it would point to a VSC-valid link which the author of the PR can use to navigate to the error as quick as possible
I will use this to better demonstrate what I'm thinking about. So the comment could be:
MainActivity.kt#L24 Unresolved reference: chikuwa
First of all great tool! 💪🏻
We are aiming to use this just for errors. The most common case for us is when production code is altered but the author is forgetting to refactor unit-tests based on the changes of production code. In that case a non-inlined comment will be posted to PR since the unit-tests have not been altered yet. This comment though contains very little information in regards to where the error is located.
So it would be nice to maybe:
I will use this to better demonstrate what I'm thinking about. So the comment could be:
MainActivity.kt#L24 Unresolved reference: chikuwa