Hi @crisbeto, first and foremost, thanks again for taking this on! I ran this migration in g3 and it was very helpful to identify that places that needed updates. I noticed a couple things:

• There were quite a few false positives with our strategy for the observable. A lot of the subscriptions either didn't even uses the fragment or were checking the truthy/falsey-ness of it.
• I've noticed with this one and with other migrations that if there is a leading comment on the node we're modifying, we end up copying the comment into the migrated node, resulting in a duplicated comment
• I'm going to send out the CLs for the remaining changes (I quickly checked each by hand and reverted a bunch). Based on the feedback from that, it might be that we should use this as a g3-only migration and let external users migrate their uses by hand. I think this should be a relatively small amount of work for those who are upgrading and the experience might be better than if we incorrectly migrate something (as noted in the first bullet point).

@atscott I've reworked the migration so that it only applies to ActivatedRouteSnapshot.fragment.

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.}