Config: allow to set maps on null value

[rht]

Also, now, if ipfs config foo.bar has value of anything that is not map (0, "0", 0.1),
then ipfs config foo.bar.baz now returns an error instead of a panic

Fixes #1561

[GitCop]

There were the following issues with your Pull Request

• Commit: c6d1413
  • Invalid signoff. Commit message must end with
    License: MIT
    Signed-off-by: .* <.*>

Guidelines are available to help. Your feedback on GitCop is welcome on this issue

---

This message was auto-generated by https://gitcop.com

[GitCop]

There were the following issues with your Pull Request

• Commit: 183a524
  • Invalid signoff. Commit message must end with
    License: MIT
    Signed-off-by: .* <.*>

Guidelines are available to help. Your feedback on GitCop is welcome on this issue

---

This message was auto-generated by https://gitcop.com

[whyrusleeping]

Does this mean we can set config values that dont actually exist in the config struct? like foo.bar.baz?

[rht]

This was already possible before. The PR makes it that if one of the key is null, it can be overwritten with a map (bar with value null -> bar.baz).

[whyrusleeping]

@rht okay, seems fine to me then

[jbenet]

I just realized that afbdedb was before c0a0cde, which means one commit fails tests -- let's order things such that no commit fails tests. otherwise hard to rebase.

(this (and github's lack of "issuing a test per commit" is why https://github.com/jbenet/git-push-each exists))

[rht]

Sorry, I did remember switching the order with rebase but didn't check.