Merges two maps into one. Resolving conflicts: First, the keys of changes must equal the keys of origin,so the needless keys of changes will be drop. Second,use the key-value of origin when:
- theirs key-type are diffrent
the key of changesdoesn't exist inoriginthe originthat has key___force__will force replace for thechanges
If available in Hex, the package can be installed
by adding xy_yaml to your list of dependencies in mix.exs:
def deps do
[
{:xy_yaml, "~> 0.1.0"}
]
endDocumentation can be generated with ExDoc and published on HexDocs. Once published, the docs can be found at https://hexdocs.pm/xy_yaml.
To use this lib, you should config variable (probably in your app.config):
config :xy_yaml,
phx_name: :im_webserver, #phoenix project name
file_dir: "priv/sets/" #origin yaml file save directory,default: "priv/yamls/"iex> origin=%{k1: %{k2: %{k3: %{k4: :v4}}},k2: :v2}
...> changes=%{k1: %{k2: %{k3: %{k4: :v41,k5: :k5}}},k2: 1}
...> XyYaml.merge(changes,origin)
%{k1: %{k2: %{k3: %{k4: :v41}}},k2: :v2}iex> origin=%{"k1" => %{"k2" => %{"k3" => %{"__force__" => true, "k4" => "force_replace"}}},"k2" => "v2"}
...> changes=%{"k1" => %{"k2" => %{"k3" => %{"k4" => "v42"}}}, "k2" => "v2_changes"}
...> XyYaml.merge(changes,origin)
%{"k1" => %{"k2" => %{"k3" => %{"k4" => "force_replace"}}},"k2" => "v2_changes"}