Skip to content

Conversation

@clavedeluna
Copy link
Contributor

Overview

One sentence, high-level explanation of WHY changes are introduced and/or business need

Description

  • What/WHY/how these changes are needed

Additional Details

  • Any follow up tickets or discussion
  • Any specific merge / deploy details

@sonarqubecloud
Copy link

sonarqubecloud bot commented Dec 4, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud


class ResultSet(dict[str, dict[Path, list[Result]]]):
results_for_rule: dict[str, list[Result]]
class Rule(CodetfRule):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@clavedeluna what if instead of being prescriptive about the specific metadata fields here, we instead add a field with an abstract type that conforms to some API like get_metadata_summary() -> str and allow each tool to define the way they want to present it?

I also don't want to overengineer this without having a lot of examples to work with.

@clavedeluna clavedeluna closed this Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants