Expose new models created after the explorer is initiated

[raymondfeng]

/to @ritch or @bajtos

The PR fixes the issue that models remoted after the explorer is initiated are not visible.

It depends on strongloop/loopback#402

[bajtos]

I believe it should be easy to filter routes for a given class only - see the code in addRouteToAPISpec which is looking up the class name and shared class using the route metadata.

Once we have a function "return the sub-array of routes that are for the given class", this hack will be no longer necessary.

[jsheely]

Please ensure that strongloop/loopback#686 is complete before merging in this fix.

Many members in the community would like to have remote methods that are invisible to the /explorer UI but can be called if you know about them. "secret endpoints" if you will.

[AurelieV]

@raymondfeng any evolution for this PR? Now that explorer is in a component, the workaround of defining the boot script before the explorer is not possible.
So how is it possible to add a remote method in boot script, and see it in explorer?

[superkhau]

@raymondfeng Is this PR still relevant? It was opened in 2014, if not lets just close this.

[richardpringle]

Closing.... we can re-open if necessary

[kristojorg]

Is there any way to expose remote methods added in a boot script?

[bajtos]

@kristojorg

Is there any way to expose remote methods added in a boot script?

There is already work in progress to implement this feature. See #208 and strongloop/loopback#3322

Unfortunately, #208 looks pretty much abandoned. Would you like to take it over, add the required test and submit as a new pull request?