silverdr
Using Phoenix.LiveView.TagEngine as an EEx.Engine is deprecated!
To compile HEEx, use Phoenix.LiveView.TagEngine.compile/2 instead.
Started getting this deprecation notice. Any quick fixes to how my heex stuff is compiled so that this warning goes safely away?
P. S. There is no longer a separate Phoenix section/category, is there?
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m aware of 2 such projects, are there others?
git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
Hi all,
I’m working on a Phoenix project where I need to make external HTTP requests and I’m trying to choose between Req and HTTPoison....
New
Hi everyone.
My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
Hi,
we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New
Hi all, I’m new here and would like to hear peoples views on my Elixir/Phoenix based game-engine! :smiley:
Mutonex gamedesign was finish...
New
Hello
I’ve been coding in Elixir for almost two years now because of my current job where we implemented Elixir in our application. But ...
New
Other Trending Topics
Hey there,
I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first.
...
New
Hi everyone :waving_hand:
I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #hex











Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
rhcarvalho
This was an optimization/refactoring in LiveView. The relevant PR is Refactor TagEngine introducing TagEngine.Compiler by SteffenDE · Pull Request #4125 · phoenixframework/phoenix_live_view · GitHub
silverdr
Right… and what am I missing that I get those warnings?
FWIW - I see
Phoenix.LiveView.TagEngine(or evenTagEnginealone) nowhere in the project files. And I get warnings on myheexstuff.steffend
I improved the warning to include the file + line. It could very well be from a dependency. Please try 1.2.5!
silverdr
Thank you. That might help. I’ll check and report.
silverdr
I am sorry it took so long, but – TBH – I got a bit puzzled. I switched to 1.2.5 and… these particular warnings disappeared. Then I spent some time checking whether I might have changed something else but didn’t recall or find anything related. Temporarily rolled back some seemingly unrelated changes but no warnings reappeared. I should have rolled back more and especially LV too, but I had to do some urgent changes and didn’t get back to this until now. All in all - the issue seems to have solved itself, even if I don’t know how
In any case - thank you for your fast reaction.
rhcarvalho
Nice to hear it’s gone without requiring additional work. And if it ever comes back the improved reporting by Steffen will make addressing the issue a precise and hopefully quick task!