-
Notifications
You must be signed in to change notification settings - Fork 58
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
AF-3731: Carry type parameters on generated empty prop/state mixins classes #220
Conversation
Security InsightsNo security relevant content was detected by automated scans. Action Items
Questions or Comments? Reach out on Slack: #support-infosec. |
var baz; | ||
} | ||
'''); | ||
List<T> bar; |
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.
T
isn't actually defined in this example
|
||
test('with type parameters', () { | ||
preservedLineNumbersTest(''' | ||
@PropsMixin() class FooPropsMixin<T> { |
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.
Just to be safe, let's use two params and have one of them use a bound as well to make sure that all works:
FooPropsMixin<T extends Iterable<T>, U>
Codecov Report
@@ Coverage Diff @@
## master #220 +/- ##
======================================
Coverage 90.1% 90.1%
======================================
Files 35 35
Lines 1767 1767
======================================
Hits 1592 1592
Misses 175 175 |
QA +1
|
@Workiva/release-management-p |
Ultimate problem:
The transformer does not carry props/state mixins that have type parameters through to the generated
$
prefixed class. Example:How it was fixed:
Carry type parameters from the declared props/state mixin class and add tests.
Testing suggestions:
Potential areas of regression:
Mixin generation