Cheers Andy. I’m really starting to question myself now and I don’t know if it’s because I’m being really stupid, or I just suck at explaining what I was trying to achieve. Taking your inline macros, much like the ones at the top, I’m still unable to get Phoenix to evaluate EEx tags inside the SVG.
I’ve put a really quick example up https://github.com/samgaw/dyn_img
I’m definitely missing something - the inline SVG macros above are designed to be used like:
<button class="btn btn-primary mb2 btn-ple" style='margin-left: 5px' type='submit'>
#{ Svg.inline("SquareOk") }
</button>
(from the code AndyL linked)
But if you’ve got EEx markup that needs to be compiled into a function to return the SVG, it seems like render with an .svg.eex partial should do the right thing:
<div class="place-where-svg-goes">
<%= render("my_template.svg", some_param: "foo") %>
</div>
What about the render approach doesn’t work for your use case?
render works fine. It just gets a little unwieldy as the number of components increases and they start getting shared between views. Which is why I was saying I’ll maybe get a chance to revisit it at some stage to find a more elegant approach to structuring them in a project e.g. helper macros + a different pattern on use Phoenix.View, root: "".
Using the inline macros for styling elements genuinely wasn’t a use case I’d consider so it makes now why I was confused with responses here 