Skip to content

fix: correct inheritance fields issue - #8

Merged
arnaud-thorel-of merged 1 commit into
mainfrom
fix/correct-inheritance-fields
Mar 25, 2026
Merged

fix: correct inheritance fields issue#8
arnaud-thorel-of merged 1 commit into
mainfrom
fix/correct-inheritance-fields

Conversation

@arnaud-thorel-of

Copy link
Copy Markdown
Contributor

Summary

  • FilterFieldAnnotationScanner scannait uniquement les champs déclarés directement sur la classe (getDeclaredFields()), ignorant les champs hérités des classes parentes
  • Ajout de getAllFields() qui remonte la hiérarchie de classes jusqu'à Object
  • Ajout de DummyRequestWithInheritance (extend DummyRequest + 1 champ) et du test shouldScanInheritanceFieldsModel qui vérifie les 7 filtres (6 du parent + 1 hérité)

Test plan

  • shouldScanInheritanceFieldsModel : vérifie que 7 filtres sont retournés pour une classe héritée
  • shouldScanModel et shouldScanGroupMultiFieldModel : non-régression

🤖 Generated with Claude Code

Scan all fields from the class hierarchy (class + superclasses) instead
of only declared fields of the direct class.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@sonarqubecloud

Copy link
Copy Markdown

@arnaud-thorel-of
arnaud-thorel-of merged commit 971859c into main Mar 25, 2026
3 checks passed
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.

1 participant