dpreston
Is there a built-in way to decode json that has a list of objects that are not decoded to the same struct, and the list is not at the root of the json?
Its a large, deeply nested json payload from a 3rd party, and I would prefer not to recursively decode and replace each list, but thats the only solution I have so far. Any suggestions would be appreciated.
Poison can do this if the list is the root,
defmodule TypeA do
defstruct shared: "", only_a: ""
end
defmodule TypeB do
defstruct shared: "", only_b: ""
end
options = fn
%{only_a: _a} -> %TypeA{}
%{only_b: _b} -> %TypeB{}
end
"""
[
{
"shared": "value",
"only_a": "A!"
},
{
"shared": "value",
"only_b": "B!"
}
]
"""
|> Poison.decode!([keys: :atoms!, as: [options]])
[
%TypeA{shared: "value", only_a: "A!"},
%TypeB{shared: "value", only_b: "B!"}
]
but if there is a parent struct, the children objects just decode to plain maps.
defmodule Parent do
defstruct children: []
end
"""
{
"children": [
{
"shared": "value",
"only_a": "A!"
},
{
"shared": "value",
"only_b": "B!"
}
]
}
"""
|> Poison.decode!( as: %Parent{})
%Parent{
children: [
%{"only_a" => "A!", "shared" => "value"},
%{"only_b" => "B!", "shared" => "value"}
]
}
I’ve tried adding the as: function to the %Parent{} struct definition, but its not a valid value.
defmodule Parent do
children = fn
%{only_a: _a} -> %TypeA{}
%{only_b: _b} -> %TypeB{}
end
defstruct children: children # <- invalid value
end
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex










Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
mudasobwa
Another option would be a custom
Poison’s encoder implementation for structs likeParent.I would nevertheless stick with straight parsing into maps and then upgrading them to structs with
update_in/3throughAccess. That’d be more explicit. Likedpreston
Thanks @mudasobwa, for prompting me to dig further into the decoders
I’ve gone with custom Poison decoders for each of the relevant structs. It’s really simple to just add the possible structs to the
children_typesin the decode function and it catches them all on the first pass instead of needing to rewalk the object until all the structs have been matched.