zlost
code
defmodule LibJasonTest do
use ExUnit.Case
defmodule Category do
@type t :: %__MODULE__{
id: Integer.t(),
name: String.t()
}
@derive Jason.Encoder
defstruct [:id, :name]
end
defmodule Book do
@type t :: %__MODULE__{
id: Integer.t(),
name: String.t(),
price: Float.t(),
categories: [Category.t()],
created_at: DateTime.t()
}
@derive Jason.Encoder
defstruct [
:id,
:name,
:price,
:categories,
:created_at
]
end
test "encode / decode" do
book = %Book{}
dbg(Jason.encode!(book))
end
end
error info
1) test encode / decode (LibJasonTest)
test/lib_jason_test.exs:33
** (Protocol.UndefinedError) protocol Jason.Encoder not implemented
for %LibJasonTest.Book{id: nil, name: nil, price: nil, categories: nil,
created_at: nil} of type LibJasonTest.Book (a struct), Jason.Encoder pr
otocol must always be explicitly implemented.
If you own the struct, you can derive the implementation specifying
which fields should be encoded to JSON:
@derive {Jason.Encoder, only: [....]}
defstruct ...
It is also possible to encode all fields, although this should be u
sed carefully to avoid accidentally leaking private information when new
fields are added:
@derive Jason.Encoder
defstruct ...
Finally, if you don't own the struct you want to encode to JSON, yo
u may use Protocol.derive/3 placed outside of any module:
Protocol.derive(Jason.Encoder, NameOfTheStruct, only: [...])
Protocol.derive(Jason.Encoder, NameOfTheStruct)
. This protocol is implemented for the following type(s): Any, Atom
, BitString, Date, DateTime, Decimal, Float, Integer, Jason.Fragment, Ja
son.OrderedObject, List, Map, NaiveDateTime, Time
code: dbg(Jason.encode!(book))
stacktrace:
(jason 1.4.1) lib/jason.ex:164: Jason.encode!/2
test/lib_jason_test.exs:36: (test)
Finished in 0.1 seconds (0.00s async, 0.1s sync)
1 test, 1 failure
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 2 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
zlost
thanks, very helpful
zachallaun
As an optimization, protocols in Elixir go through a compile-time process called consolidation, which has the “drawback” of making it impossible to add new protocol implementations at runtime. Because tests are dynamically evaluated, they live in that “runtime” category.
You can read about consolidation here. It has a note about implementing protocols in tests and offers two possible fixes, one of which is to just disable protocol consolidation in tests.