#LIVEVIEW ELIXIR CODE#
#LIVEVIEW ELIXIR OFFLINE#

The app would give us visibility into numerous backend services involved in the product and also provide monitoring capabilities for purchased goods. My team at work was recently in the situation of needing an internal app built a few weeks before the launch of an important product. Phoenix LiveView checks all of those boxes. Ideally, youвЂ™d want to spend as little time as possible on internal apps, but have them be reliable, cheap to extend, and be welcoming/maintainable by a wide variety of teammates. What also inevitably happens is that teams and non-technical stakeholders end up relying heavily on the internal tool and the lack of attention and quality end up biting you. Internal web apps tend to have some of the following qualities: theyвЂ™re important, but not customer facing because theyвЂ™re not customer facing, theyвЂ™re often hard to get time to work on or maintain - making them stagnate or have low quality the functionality is often trivial (and potentially boring) to build and itвЂ™s usually hard to get any team to own it. Aside from the programming model, LiveView itself lets you build fault-isolated components that keep the rest of your page usable with no extra code. Developers without frontend experience are also empowered to contribute given the fewer moving parts with this model. TL DR: After building a large internal web application, I found that Phoenix LiveViewвЂ™s programming model lets you build web applications in half the time and with half the number of people - compared to a single page application with a JSON API backend. Window.Learnings using Phoenix LiveView for Internal Web ApplicationsДisclaimer: Opinions expressed are solely my own and do not express the views or opinions of my employer. the normal phoenix LiveView initialization, but passing in the hooks: Window.highlightAll(this.el) // this covers LiveView patches Window.highlightAll() // this covers on page load # config/dev.exs config :bern, BernWeb.Endpoint, live_reload : [ patterns : [ ~r'priv/static/.*(js|css|png|jpeg|jpg|gif|svg)$', ~r'lib/bern_web/(live|views)/.*(ex)$', ~r'lib/bern_web/templates/.*(eex)$', ~r'posts/*/.*(md)$' # = hljs.highlight(lang, block.innerText) Create a /blog folder, put your markdown in there, andД¬onfigure Elixir to watch it for changes. NimblePublisher is a small system that sets up compiling Markdown files into In the context of a blog written with Markdown, I used

#LIVEVIEW ELIXIR CODE#

LetвЂ™s talk about it IвЂ™ll show you someД®lixir and Phoenix offer live-reloading when assets change (ie, JavaScript andД¬SS), and code-reloading when Elixir code changes. Without a LiveView site? So, the trade-off is totally worth it to me. LiveView-powered components, and how else would I be able to show them off The вЂњgainingвЂќ list is worth it to me, as an Elixir developer, because it unlocks

#LIVEVIEW ELIXIR OFFLINE#

Losing the PWA and cached offline access donвЂ™t bother me. Today donвЂ™t offer pre-compiled syntax highlighting, but I was using one, so itвЂ™sДЄ loss for me. I was initially worried that moving a static site to an Elixir-powered webДЄpplication would have too many trade-offs, but I was wrong! Many static sites With optimized images, but as far as I know, youвЂ™ll have to roll-your-own. It wouldnвЂ™t be impossible to have with a LiveView-powered blog

The biggest reason is that Elixir lacks an asset-pipeline to YouвЂ™re managing a huge static site with lots of pages perhaps look elsewhere at The вЂњgiving upвЂќ list doesnвЂ™t bother me too much, at least not on my blog. For example, when editing the post, IД¬an save the file and my dev server shows the changes almost immediately. If there arenвЂ™tДЄny other readers, then open a couple of tabs on this page, and watch theДЄ reactive local development tool-chain.

ThatвЂ™s enabled by LiveView and reacts immediately. If you didnвЂ™t notice, and if there is more than 1 current reader on thisДЄrticle, look underneath the title of this article. The ability to send UI updates from the backend to the frontend efficiently. The ability to show off LiveView-enabled components (stay tuned!) Performance, IвЂ™m not too worried about this yet, and maybe I shouldnвЂ™t be forДЄ tool-chain that I understand thoroughly and can contribute to I actually Scale static content using a CDN service. Gatsby has a great VSCode-poweredДЄ mature asset-processing pipeline to optimizeД®asier scaling if traffic gets out of hand. I outline the features I lost, I gained, and some performance

Liveview elixir