I have a bespoke lazy import solution in my Polymer2.0 app which entails putting <link rel="lazy-import" group="somegroup" title="an Optional Page Title"> elements into my template and then querying them to determine which to load when I dynamically request a load of (say) "somegroup".
Modularizer seems to have treated them just like <link rel="import"> and created static import statements for every one.
I fully accept that I should no longer be using declarative html for dynamic imports (I am thinking along the lines of modules defining arrays of import references for each group), but there is absolutely nothing in the docs that I can find that warns me that this is what Modularizer is going to do and as a result have lost (without going to a different git branch) some of my meta data.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I have a bespoke lazy import solution in my Polymer2.0 app which entails putting
<link rel="lazy-import" group="somegroup" title="an Optional Page Title">
elements into my template and then querying them to determine which to load when I dynamically request a load of (say) "somegroup".Modularizer seems to have treated them just like
<link rel="import">
and created static import statements for every one.I fully accept that I should no longer be using declarative html for dynamic imports (I am thinking along the lines of modules defining arrays of import references for each group), but there is absolutely nothing in the docs that I can find that warns me that this is what Modularizer is going to do and as a result have lost (without going to a different git branch) some of my meta data.