Repository navigation
Support using transformers + Dartium in checked mode #4560
Description
Currently, we fail with "not implemented" thrown by AbstractChangeDetector.checkNoChanges on transformed code in Dartium running in checked mode. This is because transformer decides whether to generate no-change checks separately from Dartium. Instead, we should always generate checking code, guarded by assert. This way, dart2js can tree shake these checks off for production, and the assertions will behave consistently following the checked mode option in Dartium.
Activity
feat(change_detect): Guard `checkNoChanges` behind `assertionsEnabled`
angular-automatic-lock-bot commentedon Sep 7, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.