loopback-connector-remote

History

Miroslav Bajtoš 0fd7bf06b5 Register Models with Dynamic converter Fix `RemoteConnector.prototype.resolve` to register new models with strong-remoting's `Dynamic` type resolver. Before this change, if loopback-connector-remoting ended up with its own copy of strong-remoting, then the responses were not converted from plain objects to model instances, because model converters were registered with the other instances of strong-remoting. This has a side-effect that when there is only one strong-remoting instance in the app, then there will be multiple converters registered for the same model. Since the code performing conversion takes into account the first model only, this should not pose any issues.	2016-01-26 15:13:09 +01:00
..
relations.js	Clean up tests	2016-01-07 20:08:05 -08:00
remote-connector.js	Register Models with Dynamic converter	2016-01-26 15:13:09 +01:00

Miroslav Bajtoš 0fd7bf06b5 Register Models with Dynamic converter

Fix `RemoteConnector.prototype.resolve` to register new models with
strong-remoting's `Dynamic` type resolver.

Before this change, if loopback-connector-remoting ended up with its
own copy of strong-remoting, then the responses were not converted
from plain objects to model instances, because model converters
were registered with the other instances of strong-remoting.

This has a side-effect that when there is only one strong-remoting
instance in the app, then there will be multiple converters registered
for the same model. Since the code performing conversion takes into
account the first model only, this should not pose any issues.

2016-01-26 15:13:09 +01:00

relations.js

Clean up tests

2016-01-07 20:08:05 -08:00

remote-connector.js

2016-01-26 15:13:09 +01:00