Update use of disableMethodByName

[crandmck]

Authentication, authorization, and permissions still refers to disableRemoteMethod but in 3.0 this changes to disableMethodByName per http://loopback.io/doc/en/lb3/3.0-Release-Notes.html#clean-up-of-api-for-finding-and-disabling-remote-methods

Cf #297 (comment)

[crandmck]

@bschrammIBM
To disable a static remote method use ModelName.disableRemoteMethodByName('methodname') where ModelName is the name of the model and methodname is the name of the method.

To disable an instance (prototype) remote method, use: ModelName.disableRemoteMethodByName('prototype.methodname')

[bschrammIBM]

@bajtos The old command disableRemoteMethod is still in the loopback api reference at the following location: https://apidocs.strongloop.com/loopback/#model-disableremotemethod
Just wanted to confirm it was supposed to remain in the API reference.

[bajtos]

The old command disableRemoteMethod is still in the loopback api reference at the following location: https://apidocs.strongloop.com/loopback/#model-disableremotemethod
Just wanted to confirm it was supposed to remain in the API reference.

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!).

[bschrammIBM]

@crandmck Is there a way to mark a method as "Deprecated" in the API docs?

[crandmck]

Yes, put "deprecated" in the doc comment in the code ;-) I'll take care of that.

[bschrammIBM]

Closing this issue. The update is now posted on loopback.io/docs.