-
Notifications
You must be signed in to change notification settings - Fork 80
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
CIF-1220: Fix CQBP-84 violation for Venia Reference #261
Conversation
- remove @ProviderType annotation if the interface is implemented / extended by custom code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The @ProviderType
is actually set on all the Sling models, shouldn't we remove this in all the models? Customers might extend other components, the product teaser is just an example. We should check how this is done in the WCM core components, I checked a few and they had either @ConsumerType
or nothing (which defaults to consumer type). WDYT?
I think we should remove @ProviderType for all models unless we decide which ones should be "final" (if any). Indeed the WCM core components models are all @ConsumerType (explicit or implicit) |
+1 for |
- remove @ProviderType annotation from all component models
Removed |
Codecov Report
@@ Coverage Diff @@
## master #261 +/- ##
=========================================
Coverage 62.32% 62.32%
Complexity 728 728
=========================================
Files 171 171
Lines 5240 5240
Branches 820 820
=========================================
Hits 3266 3266
Misses 1862 1862
Partials 112 112
Continue to review full report at Codecov.
|
Description
Remove @ProviderType annotation if the interface is implemented / extended by custom code.
This fixes CM code quality reported issue:
Related Issue
https://jira.corp.adobe.com/browse/CIF-1220
Motivation and Context
Custom component models should not implement / extend core component interfaces annotated with @ProviderType to avoid breaking changes in core interface.
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: