Skip to content

Conversation

@vbochetRTE
Copy link
Collaborator

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • A PR or issue has been opened in all impacted repositories (if any)

Does this PR already have an issue describing the problem?
No

What kind of change does this PR introduce?
Feature

What is the current behavior?
The methods ExtensionConfigLoader.load, ExtensionJsonSerializer.deserialize and ExtensionJsonSerializer.deserializeAndUpdate do not take a ReportNode object as a parameter.
This prevents classes implementing these interfaces from using ReportNode in their processing.

What is the new behavior (if this is a feature change)?
The three methods listed above now have the possibility to take a ReportNode as a parameter if needed.

Does this PR introduce a breaking change or deprecate an API?

  • Yes
  • No

Other information:

@sonarqubecloud
Copy link

@olperr1 olperr1 assigned olperr1 and unassigned olperr1 Nov 18, 2025
@olperr1 olperr1 self-requested a review November 18, 2025 10:08
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.

3 participants