Ability to escape . in order to set a literal destination key

[eatplaysleep]

When the actual destination key contains . there is no way to actually set it.

Expected

Escaping . would result in setting the destination key as a literal.

Actual

Performs deep mapping.

Example

Origin

{
   "username": "some value",
   "name": "some value"
}

Map

{
   "username": "profile\.username",
   "name": "profile\.name"
}

Expected Result

{
   "profile.username": "some value",
   "profile.name": "some value"
}

Actual Result

{
   "profile": {
      "username": "some value",
      "name": "some value"
   }
}

[ptychu]

Hi @eatplaysleep,
I just tried this project for the first time. I had the same problem. It appears, that it's already possible to escape a period in destination key. It's required to use double back slash. To get your expected result you should use following map:

{
   "username": "profile\\.username",
   "name": "profile\\.name"
}

I hope it helps.

@wankdanker, I'm not sure if this should be enough to close this issue, or should single backslash escaping be supported? Perhaps mentioning this in the README.md would help to avoid confusion?