There was:

But it doesn’t seem to have been updated in a while according to hex. Also when I used that library at my last company I noticed it wasn’t that fast. So there is defiantly room for improvement.

I’m not sure it’s good to rely on a json encoder/decoder.

Also be careful about lists they are not that clear in json patch standard and can cause of lot of problems.

Thanks for your feedback

Well, my search skills fail. I will have a look at that lib for comparison. But I already saw that it offers a better error feedback. This is currently not the best for Jsonpatch. Anyhow I also have to take a deeper look at performance.

I’m not sure it’s good to rely on a json encoder/decoder.

This was historically grown. I just wanted to offer the option for mapping but I build first the encoder/decoder. I will leave it to the consumer of the lib what encoder/coder they want to use. I removed the dependency.

v0.9.0

The new release added helpful feedback on errors while patching.

In this example the test operation failed.

iex> patch = [
...> %Jsonpatch.Operation.Add{path: "/age", value: 33},
...> %Jsonpatch.Operation.Test{path: "/name", value: "Alice"}
...> ]
iex> target = %{"name" => "Bob", "married" => false, "hobbies" => ["Sport", "Elixir", "Football"], "home" => "Berlin"}
iex> Jsonpatch.apply_patch(patch, target)
{:error, :test_failed, "Expected value 'Alice' at '/name'"}

Other possible errors are :invalid_path and :invalid_index.

v0.9.3

It has been a since the last update. I worked on testing to eliminate dead code and bugs (of course). Also I tried to make the documentation a little bit prettier.

• Jsonpatch — Jsonpatch v2.3.1 |> read_documentation
• jsonpatch | Hex |> get_dependency
• GitHub - corka149/jsonpatch: A implementation of RFC 6902 in pure Elixir. · GitHub |> browse_code

I am happy about any feedback.

Your Corka/Sebastian

v0.10.0

A new minor version is out. Recently I discovered that escaping exists for ~ and /. Also “know your standard library”: I was using Enum.with_index + Enum.find which was really not clever and replaced it with Enum.fetch.

Breaking change: Jsonpatch.apply_patch/2 was not really matching the Elixir style in my opinion. Therefore it was changed and Jsonpatch.apply_patch!/2 was added.

Before:

iex> Jsonpatch.apply_patch(patch, target)
%{"name" => "Bob", "married" => true, "hobbies" => ["Elixir!"], "age" => 33}

Now:

iex> Jsonpatch.apply_patch(patch, target)
{:ok, %{"name" => "Bob", "married" => true, "hobbies" => ["Elixir!"], "age" => 33}}

In contrast Jsonpatch.apply_patch!/2 will return no tuple. Instead it will return the patched value or JsonpatchException.

Changelog:

• Made jsonpatch more Elixir-API-like by adding Jsonpatch.apply_patch! (which raise an exception) and changed Jsonpatch.apply_patch to return a tuple.
• Implemented escaping for ‘~’ and ‘/’
• Allow usage of ‘-’ for Add and Copy operation
• Fixed adding and copying values to array
• Improved error feedback of test operation
• Fixed: Replace operation adds error to target
• Cleaned code: Replaced strange constructs of Enum.with_index with Enum.fetch

Updated documentation: Jsonpatch — Jsonpatch v0.10.0

v0.11.0

The whole process for creating patches through Jsonpatch.diff/2 was not perfect. I was encouraged through a github issue to rewrite it with a reduce-loop. This version fixes this. In addition, Jsonpatch.FlatMap was removed because it is not necessary anymore and it was not the focus of this lib.

Changelog:

• Removed module Jsonpatch.FlatMap because it is not necessary anymore and not the focus of the lib
• Reworked creating diff to create less unnecessary data and for more accurate patches
• Fixed adding values to empty lists (thanks @webdeb )

Updated documentation: Jsonpatch — Jsonpatch v0.11.0

(No version update)

Thanks to Mix.install it is really easy to write a small script to create a patch with Jsonpatch.

Mix.install([:jsonpatch, :poison])

source =
  File.read!("foo.json")
  |> Poison.Parser.parse!(%{})

destination =
  File.read!("bar.json")
  |> Poison.Parser.parse!(%{})

patch =
  source
  |> Jsonpatch.diff(destination)
  |> Jsonpatch.Mapper.to_map()

IO.inspect(patch, label: :patch)

It is so small. I love it.

v0.12.0

After a long time a new release was published.

Previously Jsonpatch sorted the patches before applying them when they were provided as list. This was wrong.
The RFC says that they should be applied in the order as they appear in the list.

This change can affect the result of applying multiple JSON patches.

Updated documentation: Jsonpatch — Jsonpatch v0.12.0

v0.12.1

The new version brings a better order for generated patches by Jsonpatch.diff/2 when lists were compared.

Before v0.12.1

iex(1)> source = %{"list" => []}
%{"list" => []}
iex(2)> destination = %{"list" => [1,2]}
%{"list" => [1, 2]}
iex(3)> Jsonpatch.diff source, destination
[
  %Jsonpatch.Operation.Add{path: "/list/1", value: 2},
  %Jsonpatch.Operation.Add{path: "/list/0", value: 1}
]

With v0.12.1

iex(1)> source = %{"list" => []}
%{"list" => []}
iex(2)> destination = %{"list" => [1,2]}
%{"list" => [1, 2]}
iex(3)> Jsonpatch.diff source, destination
[
  %Jsonpatch.Operation.Add{path: "/list/0", value: 1},
  %Jsonpatch.Operation.Add{path: "/list/1", value: 2}
]

Now the created patches can be directly applied and will created the expected destination.

Thanks @smartepsh for the PR

v0.13.0

A new version is out. It is finally possible to patch maps with atoms as keys.

The new option for apply_patch was inspired by Jason.

New option:

• :keys - controls how parts of paths are decoded. Possible values:
  • :strings (default) - decodes parts of paths as binary strings,
  • :atoms - parts of paths are converted to atoms using String.to_atom/1,
  • :atoms! - parts of paths are converted to atoms using String.to_existing_atom/1

Example

iex(1)> source = %{role: "Developer"}
%{role: "Developer"}

iex(2)> target = %{role: "Developer", team: "A"}
%{role: "Developer", team: "A"}

iex(3)> patch = Jsonpatch.diff source, target
[%Jsonpatch.Operation.Add{path: "/team", value: "A"}]

iex(4)> Jsonpatch.apply_patch patch, source, keys: :atoms
{:ok, %{role: "Developer", team: "A"}}

Cheers
Sebastian