Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add checker name to analysis.Diagnostic #43

Open
ccoVeille opened this issue Feb 6, 2025 · 7 comments · May be fixed by #50
Open

Add checker name to analysis.Diagnostic #43

ccoVeille opened this issue Feb 6, 2025 · 7 comments · May be fixed by #50

Comments

@ccoVeille
Copy link
Contributor

Following work started with #31

And settings added via #42

All reported errors could now be identified by a unique name

We can use the checker argument in newAnalysisDiagnostic

func newAnalysisDiagnostic(

@ccoVeille ccoVeille changed the title Add diagnosis to er Add checker name to analysis.Diagnostic Feb 6, 2025
@ccoVeille
Copy link
Contributor Author

Implementation question about checker names, the ones reported by the diagnosis

Are they limited to

  • integer-format
  • error-format
  • string-format
  • bool-format
  • hex-format

0r are there reported with the sub checker linked to its option ?

  • integer-format
  • integer-format.int-conversion
  • error-format
  • error-format.errorf
  • error-format.err-error
  • string-format
  • string-format.sprintf1
  • string-format.strconcat
  • bool-format
  • hex-format

@catenacyber
Copy link
Owner

Are they limited to

integer-format
error-format
string-format
bool-format
hex-format

Yes :-)

@ccoVeille
Copy link
Contributor Author

@mmorel-35 you were the one who brought the idea of adding the checker name. Wanna do it?

@mmorel-35
Copy link
Contributor

Thank you for the offer @ccoVeille , I don't have the bandwidth right now so if anyone wants to take care of it soon they are totally free to do so.
Concerning the checkers naming, I agree with @catenacyber proposition.

@ccoVeille
Copy link
Contributor Author

I accept the challenge. If you guys don't get news from me. Feel free to take it back.

@ccoVeille
Copy link
Contributor Author

ccoVeille commented Feb 7, 2025

@catenacyber
Copy link
Owner

No longer blocked

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants