You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In a few of our apps the testing setup is a little incomplete which sometimes causes "svg could not be found" warnings on the console. I'd like to ensure that such warnings are not ignored, by making the test fail when an inlined SVG could not be found.
Describe the solution you'd like
I was thinking that maybe a strict: true/false option could be added to the svgJar object in the ember-cli-build.js file. To not make this a breaking change it would be false by default, but people could set it to true for their dev and test environment builds.
The makeSvg() helper would then look at the state of that flag and either console.warn() like we do today, or throw new Error() if strict is true.
hmm, thinking some more about this, I guess it would also be nice if in production mode we could trigger a Sentry error report instead of showing the warnings, so maybe it would be better to generally be able to overwrite the warning handler. 🤔
🍩 Feature Request
Is your feature request related to a problem? Please describe.
In a few of our apps the testing setup is a little incomplete which sometimes causes "svg could not be found" warnings on the console. I'd like to ensure that such warnings are not ignored, by making the test fail when an inlined SVG could not be found.
Describe the solution you'd like
I was thinking that maybe a
strict: true/false
option could be added to thesvgJar
object in theember-cli-build.js
file. To not make this a breaking change it would befalse
by default, but people could set it totrue
for theirdev
andtest
environment builds.The
makeSvg()
helper would then look at the state of that flag and eitherconsole.warn()
like we do today, orthrow new Error()
ifstrict
istrue
.Describe alternatives you've considered
I've hacked it together for now, but this is probably not a good long-term solution to the problem.
Additional context
The text was updated successfully, but these errors were encountered: