You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So far, disableRemoteMethod has been only deprecated, it wasn't removed yet. It would be great if API docs could show the method as deprecated. Alternatively, I am fine with removing the method from API docs (but still keeping it in the public API!).
Activity
crandmck commentedon Jun 21, 2017
@bschrammIBM
To disable a static remote method use
ModelName.disableRemoteMethodByName('methodname')whereModelNameis the name of the model andmethodnameis the name of the method.To disable an instance (prototype) remote method, use:
ModelName.disableRemoteMethodByName('prototype.methodname')bschrammIBM commentedon Jun 24, 2017
@bajtos The old command
disableRemoteMethodis still in the loopback api reference at the following location: https://apidocs.strongloop.com/loopback/#model-disableremotemethodJust wanted to confirm it was supposed to remain in the API reference.
bajtos commentedon Jun 26, 2017
So far,
disableRemoteMethodhas been only deprecated, it wasn't removed yet. It would be great if API docs could show the method as deprecated. Alternatively, I am fine with removing the method from API docs (but still keeping it in the public API!).bschrammIBM commentedon Jun 26, 2017
@crandmck Is there a way to mark a method as "Deprecated" in the API docs?
crandmck commentedon Jun 26, 2017
Yes, put "deprecated" in the doc comment in the code ;-) I'll take care of that.
bschrammIBM commentedon Jun 26, 2017
Closing this issue. The update is now posted on loopback.io/docs.