DaAnalyst
Extructure - a flexible destructure library for Elixir
Hey guys (and gals),
Letting you know I finally release this Extructure library. Here’s some info copied from its docs:
By default the library is using loose (flexible) matching, allowing for implicit structural conversions (maps, lists and tuples, from one to another). Tuple and list key pair element order are also taken loosely by default.
Supports destructure-like implicit keys (with the same name as the variable) as well as optional values, flexible keyword and key pair tuple size and order of elements, implicit transformation between a map, list and a key pair tuple.
Also supports toggling between the loose mode and the standard Elixir pattern matching (“rigid”) mode where none of the flexibilities except for the optional variables are allowed.
Fully enforces pattern matching between the left and right side once taken into account the optional values and structural transformation.
For example, instead of:
%{
first_name: fist_name,
last_name: last_name,
} = socket.assigns
age = socket.assigns[ :age]
just write:
%{ first_name, last_name, _age} <~ socket.assigns
or implicitly transform the map into a list:
[ first_name, last_name, _age] <~ socket.assigns
or use a different order:
[ last_name, _age, first_name] <~ socket.assigns
or set a default value:
[ last_name, age( 25), first_name] <~ socket.assigns
Enjoy!
Most Liked
DaAnalyst
New features available in v0.2.1 (as per the changelog):
Enhancements
- Support transforming entire structures on the right side by specifying an empty map, tuple or list, e.g.:
[ a: a = %{}] <~ [ a: [ b: 2, c: 3]]
# a
# => %{b: 2, c: 3}
- Support destructuring from module (named) structures as if plain maps, e.g:
[ hour, minute, second] <~ DateTime.utc_now()
# => [hour: 15, minute: 44, second: 14]
DaAnalyst
Extructure v1.0 is out
DaAnalyst
Thanks for the compliments.
As for your question, it’s not like I had that option. Namely, the following generates a syntax error:
%{ a, b \\ 25} <~ %{ a: 1, b: 2}
as it does not work for maps, and I wanted to have a uniform way of expressing the variables (the same syntax works with lists and tuples).
hst337
Hmm, yeah, for maps the only valid syntax is left => right, left: right and variable, call(args). I’ve experienced the similar issue here: Using map syntax %{} as list brackets for integers · Issue #10964 · elixir-lang/elixir · GitHub
pejrich
Is there anyway to do use this in function heads? I find function heads like:
def func(%{"variable1" => variable1, "variable2" => variable2}) do
can get quite verbose, of course you can extract values in the first line of the function body, but sometimes having it in the function head serves additional benefits. I’ve used the Destructure library before which allows you to do the following:
def func(s(%{variable1, variable2})) do
Since your library uses slightly different syntax %{a, b} <~ vs d(%{a, b}), I was wondering if it would be possible to support function head destructuring or not.
Popular in Libraries
Other popular topics
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
Categories:
Sub Categories:
Forums
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Develop your skills with books, videos, and courses.
Enabling companies to succeed by building software people love.
The deployment platform built for Elixir: PaaS ease, VPS control.
Courses that'll move you from confusion to "Aha, now I get it!"