fix(ComponentUrlMapper): support relative template URLs in Dartium - #3743

@kegluneq this sound good. How would it work with transformers?

Good question! Right now this is a non-issue for templateUrl since we inline the template wherever possible, but I know this will be used in other places so needs to be considered there too. I imagine that means storing the component url somewhere.

Does this fall out of the compile pipeline refactor using typeImportPath? If so, maybe this should wait for that change.

Yes, the compiler refactor will actually do this automatically...

On Tue, Aug 25, 2015 at 4:07 PM Timothy Blasi [email protected]
wrote:

Good question! Right now this is a non-issue for templateUrl since we
inline the template wherever possible, but I know this will be used in
other places so needs to be considered there too. I imagine that means
storing the component url somewhere.

Does this fall out of the compile pipeline refactor
https://docs.google.com/document/d/1iVcmAaONB2ztA5GElL9pOkqcU4Gi5LNJDA0Yyp19AQA/edit#heading=h.rjublbfw3tme
using typeImportPath? If so, maybe this should wait for that change.

—
Reply to this email directly or view it on GitHub
#3743 (comment).

@tbosch Travis is happy, so now I'm happy committing this for now. It's equivalent in the transformed case and better in the Dartium case, so seems like it's an overall win, even if not perfect.

WDYT?

Merging PR #3743 on behalf of @tbosch to branch presubmit-tbosch-pr-3743.

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