Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
I spent hours trying to find out why the compiler gave me this error message:
I conducted numerous google searches and asked around on Gitter which led me to a series of red herrings. I eventually stumbled into the solution in a non-official Angular article by Tero Parviainen (@teropa) SVG AND CANVAS GRAPHICS IN ANGULAR 2. I had seen the article in other Google search results, but I ignored it because I'm using Angular 8 and I was told a lot had changed in Angular since version 2.
The answer turns out to be:
Angular is supposed to be a framework to abstract these nasty details from the developer to increase productivity by reducing complexity. If you have to spend hours figuring out a leaky abstraction as in the aforementioned svg issue, then what’s the point of Angular? It’s just another layer of fecal matter upon layers of fecal matter that eventually petrifies under its own weight into matter too hard to comprehend.
Shame upon the Angular development team!
@Joebeazelman I'm sorry that you wasted a lot of time debugging the issue.
Angular's templates are expected to be html files and we never claimed that svg files are supported. SVG support as works as designed for SVG embedded into html.
The data binding in Angular always binds to properties unless you use the
Lastly, I want to point out that I see a lot of frustration in your post, but I have to remind you that the language you are using is in violation of our code of conduct. The issue tracker is a place where we want to have a constructive discussion without unnecessary emotions, shaming, or worse.
I'm going to close this issue. If you have constructive suggestions on how to make the svg support more intuitive please open a new issue, use the issue template and adhere to our code of conduct.
Thank you for understanding.