I like this suggestion of being able to name imports and change load paths.
On Tuesday, March 10, 2015 at 9:19:29 AM UTC-6, Martin Amm wrote: > > I personally think that removing the module registry was a step in the > wrong direction. I think that having to hard code file names for > dependencies is currently the weakest point in the Polymer architecture. > > I'd prefer to replace the current import like > <link rel="import" href="*../core-icons/core-icons.html* > <http://127.0.0.1:62447/components/core-icons/core-icons.html>"> > > with > <link rel="import" name="*core-icons* > <http://127.0.0.1:62447/components/core-icons/core-icons.html>"> > > and then being able to define in globally which url provides > core-icons.html. > > This would allow to e.g. replace core-icons/core-icons.html with > my-icons/core-icons.html > > It would also allow to control client side caching by e.g. starting > with /version1/core-icons.html and replace it later with a > newer /version2/core-icons.html without having to modify all imports. > > > > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/0bcf7fa0-3875-4e96-a071-ab770f2cc59c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
