Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
This is just an idea, but what about implementing using Phoenix.View(via use MyAppWeb, :view in your module)? Then assign I think has access to @conn. Then maybe work some magic to still allow Phoenix.Component syntax - but at this point, this is something I believe is a flow that might be in development. Try investigating / asking in Surface, because that is a lot more similar to React in its approach. In fact, I think Surface is where more aggressive features are pushed out, and ironed-out features get included into Phoenix. This was the case for Phoenix.Component, and HEEX.
The git repo referred in the post is pretty up to date for the web.ex file: https://github.com/kimlindholm/phoenix_component_folders/blob/master/lib/phoenix_component_folders_web.ex
Related posts
- Is Elixir or Common Lisp the best language for building a bootstrapped B2B SaaS in 2024?
- Why Elixir Is the Best Language for Building a Bootstrapped, B2B SaaS in 2024
- Elixir for Cynical Curmudgeons
- htmlgui.nvim - Create html + css + lua apps with neovim as 'browser'. ( proof of concept )
- Phoenix JSON API Pagination