- ELIXIR LIVEVIEW PRO
- ELIXIR LIVEVIEW FREE
You need to put this in contrast with programming languages in search of a problem.
I found it helpful if you can afford it.Why are Erlang and Elixir such powerful languages?Įrlang was invented to solve a problem.
The more narrow focus books are also great:.They can help fill in some of the gaps and speed up your learning. Update: many of these books are available on medium if you are a subscriber:.The Prag Prog books on elixir are all good.Stuff you have to pay for but is worth it: I wrote an overview about deploying to a cloud instance here:Īlso checkout the #deployment channel in the Elixir slack community. Once you get the basics down, There are two great non-trivial projects you can look at for advanced usage:
ELIXIR LIVEVIEW FREE
In particular, From the free starter course: lessons 3 and 4 are the best intro to what LiveView is and lessons 18 and 19 on the two tupes of LiveComponents (stateful and stateless).
ELIXIR LIVEVIEW PRO
You will want to learn them, because they are a key part of interactivity in Phoenix.Īgain, some of the best example code is the scaffolding: mix Blog Posts post title:string content:string publish:utc_datetimeĪnd I can’t recommend enough Pragmatic Studio’s LiveView Starter and Pro Courses.
Changesets: These are like mutations in GraphQL. will simply create the context and schema while will only create the schema.Īlso the project is an excellent example of of a vanilla but production ready auth setup with canonical Ecto usage. the html variant in particular is a great example of seeing how ecto ties into phoenix and how changesets work at the data layer as well as in the UI. |json create the context, schema as well as the controllers, view, templates, etc. It works best with Postgres but the major databases vendors are all supported.Ī good way to play around with Ecto is to try out the mix phx.gen scaffold generators: mix Learning EctoĮcto is the Phoenix ORM (Technically it’s not an ORM, but it certainly covers much of the featureset of an ORM. You should read the whole thing but start with the request life-cycle guide and then go back and read all the others. The official guide is quite well written. Like the entire Elixir ecosystem, this means there is a learning curve, but great velocity gains to be had once you get used to it. Paying attention to directory structure and naming conventions is much more important than in other web app frameworks. You can strongly feel the Rails influence. Phoenix is an opinionated framework with quite a bit of magic to it. 
meta-programming (macros) Learning Phoenix I do recommend skimming thru every page of the getting started guide just to get a sense of what you don’t know yet:
hexdocs: centralized documentation website. 
percent-curly braces and arrow notation: %. If you are used to arrays, some operations are O(n) such as length or append. They use the “:” prefix like :identifier or :key or :date. More like user-defined symbols or tokens. If you are familiar, it’s not a big leap. Learning Elixirįor experience programmers, the syntax is heavily Ruby inspired. It’s not particularly steep, but it is longer than a language like go but not as long as required by the Haskell or OCaml ecosystems. There is a learning curve to the ecosytem. After getting a hang of Phoenix, jump into LiveView. You can and should learn Elixir and Phoenix at the same time. In order to make web apps with Elixir, here’s a short primer on learning the language and major frameworks:įirst, don’t just learn Elixir.
0 kommentar(er)
