Skip to content

adding on started listener to display nestRemoting method in swagger …#208

Closed
flvndvd wants to merge 2 commits intostrongloop:masterfrom
flvndvd:fix/nestRemotingRoutes
Closed

adding on started listener to display nestRemoting method in swagger …#208
flvndvd wants to merge 2 commits intostrongloop:masterfrom
flvndvd:fix/nestRemotingRoutes

Conversation

@flvndvd
Copy link

@flvndvd flvndvd commented Mar 29, 2017

Description

Add nestRemoting routes in the explorer

Related issues

Checklist

  • New tests added or existing tests modified to cover all changes
  • Code conforms with the style
    guide

@slnode
Copy link

slnode commented Mar 29, 2017

Can one of the admins verify this patch? To accept patch and trigger a build add comment ".ok\W+to\W+test."

@slnode
Copy link

slnode commented Mar 29, 2017

Can one of the admins verify this patch?

3 similar comments
@slnode
Copy link

slnode commented Mar 29, 2017

Can one of the admins verify this patch?

@slnode
Copy link

slnode commented Mar 29, 2017

Can one of the admins verify this patch?

@slnode
Copy link

slnode commented Mar 29, 2017

Can one of the admins verify this patch?

Copy link
Member

@bajtos bajtos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello, thank you for the pull request.

I am afraid the event started is not the right one to use for detecting new endpoints added by nestRemoting. Consider what happens when the app calls nestRemoting well after it has started?

A better solution is to modify LoopBack to emit a new event whenever a new shared method is defined, e.g. remoteMethodAdded. Check here and here how remoteMethodDisabled is implemented - this new event can be added in a similar fashion.

Last but not least, I'll need you to add a unit-test to verify your implementation, see the test(s) for remoteMethodDisabled event for inspiration.

@bajtos
Copy link
Member

bajtos commented Mar 29, 2017

@slnode ok to test

@flvndvd
Copy link
Author

flvndvd commented Mar 29, 2017

@bajtos
updated in d0f70cc
See associated PR on strongloop/loopback#3322

Copy link
Member

@bajtos bajtos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the update. strongloop/loopback#3322 has been merged and released, let's get this part finished too.

Now I need you to add a test to verify this new feature, see my earlier comment:

Last but not least, I'll need you to add a unit-test to verify your implementation, see the test(s) for remoteMethodDisabled event for inspiration.

@bajtos
Copy link
Member

bajtos commented Apr 24, 2017

Closing as abandoned.

@bajtos bajtos closed this Apr 24, 2017
@bajtos
Copy link
Member

bajtos commented May 22, 2017

@DAVIDFlavien I am puzzled by your "thumbs down" on my #208 (comment). If you are still keen to get this finished, then please address my comments above and either reopen this pull request or send a new one.

@raymondfeng raymondfeng reopened this Sep 15, 2017
@slnode
Copy link

slnode commented Sep 15, 2017

Can one of the admins verify this patch? To accept patch and trigger a build add comment ".ok\W+to\W+test."

@slnode
Copy link

slnode commented Sep 15, 2017

Can one of the admins verify this patch?

2 similar comments
@slnode
Copy link

slnode commented Sep 15, 2017

Can one of the admins verify this patch?

@slnode
Copy link

slnode commented Sep 15, 2017

Can one of the admins verify this patch?

raymondfeng pushed a commit that referenced this pull request Sep 15, 2017
@raymondfeng
Copy link
Member

Close as I'm reworking on the PR at #222

raymondfeng pushed a commit that referenced this pull request Sep 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants