-
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
CPLAT-4476: Create workaround for ddc bug related to uninitialized maps #252
Conversation
Security InsightsNo security relevant content was detected by automated scans. Action Items
Questions or Comments? Reach out on Slack: #support-infosec. |
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.
+1
var customNamespaceProp; | ||
|
||
@Accessor(keyNamespace: 'custom namespace~~', key: 'custom key!') | ||
var customKeyAndNamespaceProp; |
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.
#nit most of these props are unused
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.
(Same goes for the other file like this)
+1 |
QA +1
Merging into master. |
Ultimate problem:
Uninitialized key-value pairs in Maps are treated differently between dart2js compiled output and ddc compiled output. Details: dart-lang/sdk#36052
How it was fixed:
Add a null aware operator and explicitly return null in generated prop/state getters when the
props
orstate
map does not contain a value for the key for any prop/state memberTesting suggestions:
Potential areas of regression:
None