A blazing fast JSON parser and generator in pure Elixir.
The parser is usually twice as fast as Poison
and only about 50% slower than
jiffy
- which is implemented in C with NIFs. On some data, Jason
can even
outperform jiffy
. With HiPE, Jason
consistently outperforms jiffy
on
all inputs by 20-30%.
The generator is also usually twice as fast as Poison
and uses less memory. It
is about 1.3 to 2.0 times slower than jiffy
depending on input.
With HiPE Jason
is 1.3 to even 2.5 times faster than jiffy
.
Both parser and generator fully conform to RFC 8259 and ECMA 404 standard. The parser is tested using JSONTestSuite.
If available in Hex, the package can be installed
by adding jason
to your list of dependencies in mix.exs
:
def deps do
[{:jason, "~> 0.1.0"}]
end
Documentation can be generated with ExDoc and published on HexDocs. Once published, the docs can be found at https://hexdocs.pm/jason.
You need to define a custom "types" module:
Postgrex.Types.define(MyApp.PostgresTypes, [], json: Jason)
## If using with ecto, you also need to pass ecto default extensions:
Postgrex.Types.define(MyApp.PostgresTypes, [] ++ Ecto.Adapters.Postgres.extensions(), json: Jason)
Then you can use the module, by passing it to Postgrex.start_link
.
To replicate fully the current behaviour of Poison
when used in Ecto applications,
you need to configure Jason
to be the default encoder:
config :ecto, json_library: Jason
Additionally, when using PostgreSQL, you need to define a custom types module as described above, and configure your repo to use it:
config :my_app, MyApp.Repo, types: MyApp.PostgresTypes
First, you need to configure Plug.Parsers
to use Jason
for parsing JSON. You need to find,
where you're plugging the Plug.Parsers
plug (in case of Phoenix, it will be in the
Endpoint module) and configure it, for example:
plug Plug.Parsers,
parsers: [:urlencoded, :multipart, :json],
pass: ["*/*"],
json_decoder: Jason
Additionally, for Phoenix, you need to configure the "encoder"
config :phoenix, :format_encoders,
json: Jason
A custom JSON encoder for Phoenix channels is unfortunately a bit more involved, thw whole procedure is described in here.
You need to pass the :json_codec
option to Absinthe.Plug
# When called directly:
plug Absinthe.Plug,
schema: MyApp.Schema,
json_codec: Jason
# When used in phoenix router:
forward "/api",
to: Absinthe.Plug,
init_opts: [schema: MyApp.Schema, json_codec: Jason]
Benchmarks against most popular Elixir & Erlang json libraries can be executed
with mix bench encode
and mix bench decode
.
A HTML report of the benchmarks (after their execution) can be found in
bench/output/encode.html
and bench/output/decode.html
respectively.
Jason has a couple feature differences compared to Poison.
- no support for pretty printing.
- no support for decoding into data structures (the
as:
option). - no built-in encoders for
MapSet
,Range
andStream
. - no support for encoding arbitrary structs - explicit implementation
of the
Jason.Encoder
protocol is always required.
If you require encoders for any of the unsupported collection types, I suggest adding the needed implementations directly to your project:
defimpl Jason.Encoder, for: [MapSet, Range, Stream] do
def encode(struct, opts) do
Jason.Encode.list(Enum.to_list(struct), opts)
end
end
If you need to encode some struct that does not implement the protocol, 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 used 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,
you may use Protocol.derive/3
placed outside of any module:
Protocol.derive(Jason.Encoder, NameOfTheStruct, only: [...])
Protocol.derive(Jason.ENcoder, NameOfTheStruct)
Jason is released under the Apache 2.0 License - see the LICENSE file.
Some elements of tests and benchmakrs have their origins in the Poison library and were initially licensed under CC0-1.0.