sfba.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance for the San Francisco Bay Area. Come on in and join us!

Server stats:

2.3K
active users

#myelixirstatus

0 posts0 participants0 posts today

🚀 New Releases! Along with the roadmap update, I'm happy to announce:

- JSON-LD.ex v1.0 with JSON-LD 1.1 support
- RDF.ex v2.1 with rdf:JSON literal support
- Grax v0.6 with a new JSON type and support for ordered lists based on rdf:List

These updates lay groundwork for the DID implementation and future developments. Please refer to the respective CHANGELOGs for a comprehensive list of the changes.

#rdf#jsonld#elixir

#Elixirlang people, what are you using for displaying localized lists of countries and building international address forms in your Phoenix apps? #MyElixirStatus

It seems like the existing clones of the Ruby "countries" gem aren’t super well maintained, missing i18n, and don’t have address helpers (e.g. to answer the question if state/province is mandatory or if postal code goes before/after city).

Phoenix 1.18 is going to ship with support for daisyui.com. I wonder if upgrading might be a good opportunity for Keila to switch to daisyUI as well. Spruce up the UI a bit, simplify the markup, and finally add support for light mode.

Do any of you have thoughts on daisyUI?

daisyui.comdaisyUI — Tailwind CSS Components ( version 5 update is here )Best Tailwind Components Library - Free UI components for Tailwind CSS

It's good that the ElixirConf team is surveying people about what cities they would and would not attend an ElixirConf in.

I sat out the whole Florida era bc trans people aren't safe in Florida, so I'm not going. I know the organizers were locked into a contract, but I still wasn't going. I responded to the survey to let them know I would be following the same policy going forward. I suggest you do the same.

If you want to argue about this, consider fucking an active toaster

So Elixir 1.19 is slated to remove the Struct Update Syntax and after reading through the issue I am NOT a fan of this deprecation.

The Struct Update Syntax looks like: `%Point{p | x: 3}`

The proposed alternative is to pattern match where `p` is defined but that could be quite far from where you are updating the struct.

Here is the discussion: github.com/elixir-lang/elixir/

I'm curious what other developers think of this impending change. Are you in favor?

Instead, we should prefer pattern matching. With the type system, we already get the benefits of checking if fields exist or not, in a more reliable and extensible way. Here is an example from Live...
GitHubDeprecate struct update syntax, such as `%URI{x | ...}` · Issue #13974 · elixir-lang/elixirBy josevalim

A gap in the Elixir ecosystem that I've noticed on a couple of projects-- a mature terminal io / TUI library, particularly one that isn't just a quick and dirty wrapper around a C NIF. Maybe I need to finally learn enough rust to wrap ratatui with rustler?

Check out the completely revamped API documentation, now using scalar.com instead of the old Swagger interface: app.keila.io/api

I’ve also just added a new API for signup forms and for creating contacts with Double-Opt-In. 🚀

The OpenAPI schema is generated (and validated) using open_api_spex and the docs page is simply a static page that includes the standalone.js script from Scalar.