josefrichter
The docs say passing a non-empty list as the collectable is deprecated
This is a common pattern in test fixtures:
Enum.into([a: 1, b: 2], %{b: 3})
which basically takes attrs and overwrites “defaults” in the map
The docs say consider using Keyword.merge(collectable, Enum.to_list(enumerable))
But how do I correctly merge list into a map like above? Because Keyword.merge/2 seems to merge only list into list, and Map.merge/2 only map into map. And I don’t think I should be converting list to a map before the merge.
Any hints, please?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Elixir, Erlang & messaging conferences from Code Sync. Next up: ElixirConf US (10–11 Sep) & Code BEAM Europe (21–22 Oct), Haarlem + online.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixir-ls
- #elixirconf-us
- #ai
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
LostKobrakai
The collectable is the second parameter, which should no longer be a non empty list. The first parameter can be any list.
eksperimental
the collectable is the second argument, not the first one. So you are good there.
josefrichter
It’s
into(enumerable, collectable)So my
collectableis the map%{b: 3}- so it’s a “non-empy map” rather than “non-empty list” and therefore the deprecation warning doesn’t apply?LostKobrakai
Exactly.
eksperimental
If you are not getting a warning, and your Elixir version is updated, it is because you are not doing anything wrong.