Repowise findings

[crizah]

Used repowise to analyse a codebase, with the techstack of go, react and postgres. Few interesting findings:

• Got a few fps for my go backend on the dead code command. Go has a different import/export structure than python or other languages. To use a component within the same package, even if it is not in the same file, you dont need to import the component. The tool was flagging fps on this. Found a solution and have submitted a PR for it: fix(go): rescue same-file type references from unused_export false po… #629 (comment)

• There were some helpful findings on the dead code, a few jsx components were marked as dead code that i thought were being used, but the service was written inline instead of using the component. Later, got a very high CCN score on the same file which wrote the inline instead of using existing components. That was helpful.

• Another feature that i would like to have seen is if it could analyse my sql queries. Look for missing indexes in the health command and dead unused queries in the dead-code command.
  From what I understand right now, the graphs made only exist per language, but to analyse the dead sql queries (written in .sql files) used in my services (in .go), it would have to have a definite bridge. I was using sqlc to generate my queries which does auto generate .go files from the .sql queries, so the tool should have flagged unused queries. But I see that there is an explicit skip in place for interface methods, to mitigate the FPs, and sqlc auto generated .go files define query methods inside interfaces. Thats probably why it wasnt being flagged. But would like to see some sort of a feature for dead queries in the future?

Super helpful tool!