CRJVM 205 : Forcer l'utilisation du FetchType LAZY sur les collections dans les Entity JPA

[misterdz-mh]

Implémentation de la règle CRJVM 205

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

82.2% Coverage
0.0% Duplication

[wokier]

Duplicates #155

[github-actions]

This PR has been automatically marked as stale because it has no activity for 30 days.
Please add a comment if you want to keep the issue open. Thank you for your contributions!

[github-actions]

This PR has been automatically marked as stale because it has no activity for 30 days.
Please add a comment if you want to keep the issue open. Thank you for your contributions!

[dedece35]

I marked this PR as draft because of duplication (see above)

[github-actions]

This PR has been automatically marked as stale because it has no activity for 60 days.
Please add a comment if you want to keep the issue open. Thank you for your contributions!

[dedece35]

Hi @misterdz-mh, @wokier

several PR have worked on this same subject (FetchType Lazy instead of Eager for OneToMany et ManyToMany relations).

After worked on a complete analysis to check if this rule is relevant :

• first, I found that the rule already exists in SonarQube as a built-in rule : S6904
• secondly, no proof was found to check relevancy
• thirdly, I decided to launch an analysis with EnergyTracer tool which can do real measures

Thus I created a new PR to :

• add this analysis
• clean all old references to this same subject

Here is the PR : #487

Sorry, but I have to close this PR.
thank you for the work.