make mapToObject public

[wencagh]

It is sometimes useful to have option map StdClass object directly, because it is very often returned from other API clients implementations. It make no sense to encode response from other libraries to json to be decoded in next step in map function to StdClass object back.

[BenMorel]

Hi, there are a couple things bothering me here:

• this is a json-to-object mapping library, so it feels slightly odd for the main JsonMapper class to also map from an object
• if we're going to do this, we should rename mapToObject(), as the name does not clearly convey its intended meaning

Also, you changed the package name in composer.json in your PR!

[coveralls]

coverage: 92.475%. remained the same
when pulling f55bce2 on wencagh:main
into 74254ad on brick:main.

[wencagh]

Sorry of the last commit with package rename. It was accidentally pushed, after I rebase my fork.

As I mention, in my case I use this library in combination with another one, wich give me response (originaly in JSON) but automatically transformed to StdClass (no simple option how to change this behaviour]. Without making mapToObject public, there will be need to encode it back to JSON and then call map -> back to StdClass and then map it.

In question of changin name of the method, will be OK mapToObject -> mapStdClassToObject ?