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
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello!
Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app.
I creat...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
I’m trying to set up Emacs with elixir-ls via lsp-mode and credo via Flycheck. This should mostly be preconfigured as Flycheck picks up c...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
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
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
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #ai
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










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!