marcandre
While Phoenix.View#render/3 used to set @view_module and @view_template for us to be used within the layout.
WIth the newer Phoenix.View 1.0.0, is there a way to access this information?
From the doc and the source, it looks like this has to be repeated explicitly now
anyone knows why?
# now we need some extra lines...
Phoenix.View.render(SomeModule, "some_template", assigns
|> Keyword.merge(
view_module: SomeModule,
view_template: "some_template"
))
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,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
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
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted”
Version...
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
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
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
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
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
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
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security










Showing Posts 1 to 7- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
josevalim
Those functions have been moved to Phoenix.Controller.view_module/view_template. The reason is because those concepts are not very clear (or very useful) in some abstractions like LiveView, so we realized it belongs upstream. I believe it was properly deprecated and there should be CHANGELOG entries. If you are not rendering from the controller, then you have to set it yourself.
marcandre
Thanks. I wish I understood better, it still seems quite strange to me that an explicit call to
Phoenix.View.renderwouldn’t pass along the relevant information to the layout, and this seems quite remote from LiveView.I opened Change wording on Changelog by marcandre · Pull Request #4571 · phoenixframework/phoenix · GitHub as the only reference in the Changelog was as a deprecation when this is actually a breaking change.
The upgrade guide is sadly a gist, so no PR possible. Could we consider moving it to the repo?
axelson
I’d like to give a +1 on this as well. I’ve wanted to make PR’s to improve the upgrade guide as well.
marcandre
I created a PR for it… Import upgrade instructions from gist by marcandre · Pull Request #4585 · phoenixframework/phoenix · GitHub
thojanssens1
What do you use in your template now?
I have the following code
allowing to set a title for each page, which I now replaced by this horrible code:
LostKobrakai
In the template:
In the view module of the template:
There’s no need to keep all that logic in the template itself.
thojanssens1
Thank you!!