I'm afraid that's the cost right now. I highly doubt the template parser will start supporting SVG files natively. As you want to use template bindings in your SVG, it needs to be available to the compiler during *build* time. If you let go of the template bindings and use native DOM manipulation, you can pull in the SVG dynamically. But that has it's downsides too.
You can always put in a feature request in on Github. If enough people think this is a good idea, there might be native support for SVG files in the future! Regards Sander -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
