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 in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app?
Looking for hints regarding:
Addi...
New
Hi all, I wanted to ask how the community is dealing with post-release steps.
Today we have Ecto migrations, which make sure that the db...
New
Kia ora,
We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
Hello,
I have an Elixir backend that implements a custom protocol over TCP. I want to load test the backend and assess the performance o...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex










First 6 of 6 Posts
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!