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
Describe the bug
REST router currently refreshes excessively due to refreshRouter() directly refreshing the Express router instead of scheduling a refresh based on a timeout, much like registerRoute() and registerConduitRoute() already do.
To Reproduce
Set a breakpoint in REST controller's refreshRouter()
Debug Core by itself
Notice excessive refreshes
N of refresh calls would differ based on previously registered routes, but on a fresh Redis state it should be 1.
Expected behavior refreshRouter() should schedule a router refresh instead of directly refreshing Express.
The text was updated successfully, but these errors were encountered:
Describe the bug
REST router currently refreshes excessively due to
refreshRouter()
directly refreshing the Express router instead of scheduling a refresh based on a timeout, much likeregisterRoute()
andregisterConduitRoute()
already do.To Reproduce
refreshRouter()
N of refresh calls would differ based on previously registered routes, but on a fresh Redis state it should be 1.
Expected behavior
refreshRouter()
should schedule a router refresh instead of directly refreshing Express.The text was updated successfully, but these errors were encountered: