Elixir

cross-posted from: https://feddit.uk/post/24662731

Good oldcourses being irrelevant within 6 months but still trying to con people by saying they're updated to current year.

Hi! Is there anything like hackingwithswift (preferably as 100 days of SwiftUI) but focused on elixir and phoenix?

Announcing the official Elixir Language Server team to work on the code intelligence infrastructure to be used across tools and editors

Bonfire Expeditions - Collaborating to Release Version 1.0

Releasing the stable 1.0 version of the Bonfire federated social network requires collaboration with the communities, hackers, tinkerers, and sysadmins who plan to use it.

The first released candidate of LiveView 1.0 is out!

📘📘📘 New post: 10 @elixir gotchas!

It's a great language, but some behavior can be unintuitive, confusing and in the worst case lead to bugs. In this post I wanna help clear some of them up!

https://pragtob.wordpress.com/2024/05/01/10-elixir-gotchas/

You can read his book, but you can also join his talks and trainings!
Saša Jurić is our speaker and trainer at Code BEAM America in San Francisco in March and at ElixirConf EU in Lisbon in April.

See you there! Tickets:
🔥 codebeamamerica.com
🔥 elixirconf.eu

#myelixirstatus #elixirinaction #elixirlang #codebeam #elixirconf #elixirconfeu #codebeamamerica @ManningPublications @elixir @sasajuric

RE: https://hachyderm.io/users/sasajuric/statuses/111896306303158921

Elixir is a dynamically-typed functional language running on the Erlang Virtual Machine, designed for building scalable and maintainable ...

Published: Tail-Recursive & Body-Recursive Function Performance Across Elixir & BEAM versions – what’s the impact of the JIT?

Watch me go through @elixir and erlang versions from 1.6 @ OTP 21 up to 1.16 @ OTP 26 and marvel at our performance gains.

https://pragtob.wordpress.com/2024/01/08/tail-recursive-body-recursive-function-performance-across-elixir-beam-versions-whats-the-impact-of-the-jit/

This only comes around once a year and is a great time to pick up some of their great courses using promo code 2023THANKS.

• Elixir & OTP ~~$149~~ down to $89
• Phoenix LiveView ~~$129~~ down to $77
• Full-Stack GraphQL with Phoenix ~~$99~~ down to $59

at https://hexdocs.pm/open_api_spex/3.2.0/readme.html there's a definition of a module User

defmodule MyApp.Schemas do
  alias OpenApiSpex.Schema

  defmodule User do
    @behaviour OpenApiSpex.Schema
    @derive [Jason.Encoder]
    @schema %Schema{
      title: "User",
      description: "A user of the app",
      type: :object,
      properties: %{
        id: %Schema{type: :integer, description: "User ID"},
        name:  %Schema{type: :string, description: "User name"},
        email: %Schema{type: :string, description: "Email address", format: :email},
        inserted_at: %Schema{type: :string, description: "Creation timestamp", format: :datetime},
        updated_at: %Schema{type: :string, description: "Update timestamp", format: :datetime}
      },
      required: [:name, :email],
      example: %{
        "id" => 123,
        "name" => "Joe",
        "email" => "[email protected]"
      }
      "x-struct": __MODULE__
    }
    def schema, do: @schema
    defstruct Map.keys(@schema.properties)
  end

In order to avoid re-describing it like that for Open API Specs whilst having already done so for Ecto, is it possible to combine the two definitions in a single module somehow? That is, my Ecto schema User would serve its purpose for Open API Specs too. With some required tweaks.

And if I do combine them, won't this mess up with the methods of the 2 modules and other things?