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
The sockets hook is documented to be disable-able via a .sailsrc file. However, if the project dependencies are installed with npm 3, they are flattened into the project's node_modules folder. This causes Sails to detect it as a user hook (because it has a "isHook": true in its package.json) and load it anyway.
I have not checked in much detail how the hook loading works, but it seems core hooks are loaded independently of user hooks. A solution might be to treat them all equal - i.e. get the list of core hooks, get the list of user hooks, apply configuration from .sailsrc and load them.
As a nice side-effect, we would be able to disable installed user hooks via .sailsrc.
The text was updated successfully, but these errors were encountered:
The
sockets
hook is documented to be disable-able via a .sailsrc file. However, if the project dependencies are installed with npm 3, they are flattened into the project's node_modules folder. This causes Sails to detect it as a user hook (because it has a"isHook": true
in its package.json) and load it anyway.I have not checked in much detail how the hook loading works, but it seems core hooks are loaded independently of user hooks. A solution might be to treat them all equal - i.e. get the list of core hooks, get the list of user hooks, apply configuration from .sailsrc and load them.
As a nice side-effect, we would be able to disable installed user hooks via .sailsrc.
The text was updated successfully, but these errors were encountered: