Polymer: [3.0] Consider renaming polymer.js
The file /polymer.html was named so for backwards compatibility with Polymer 1.0, so that hybrid elements could use the same import. We don't have this constraint with 3.0, and could rename polymer.js to polymer-legacy.js, which would allow us to create a new polymer.js with only modern exports.
justinfagnani
All 7 comments
Why break everyone that need to stick with polymer 1 - 2 for a fair while ?
Instead use a new name for polymer 3.0. maybe polymer 3.js
joeblew99
on 28 Aug 2017
This change--if we make it--wouldn't affect 1.x or 2.x at all--they import an html file, not a js file. You'll need to change how you import polymer when you go from 2 to 3 whether or not we make this change.
arthurevans
on 28 Aug 2017
ah i missed the .html and .js. Makes sense now. thanks @arthurevans
joeblew99
on 29 Aug 2017
Move backwards compatibility version to -legacy is better. I like always keep polymer.html|js as modern.
baocang
on 29 Aug 2017
If we choose to do this, we can do it one of two ways: Hard-code a filename remapping in polymer-modulizer, or add the ability to make a directive in a file to have modulizer rename it:
ie, in polymer-element.html:
<!-- modulizer-rename: polymer.js -->
(Blocked on https://github.com/Polymer/polymer-modulizer/pull/354.)
bicknellr
on 9 Mar 2018
367 is merged.
bicknellr
on 28 Mar 2018
Related issues
yordis
路
3Comments
bmodeprogrammer
路
3Comments
mbana
路
3Comments
abdonrd
路
4Comments
yuihiro
路
3Comments
Most helpful comment
This change--if we make it--wouldn't affect 1.x or 2.x at all--they import an html file, not a js file. You'll need to change how you import polymer when you go from 2 to 3 whether or not we make this change.