This repository was archived by the owner on Jun 24, 2025. It is now read-only.
This repository was archived by the owner on Jun 24, 2025. It is now read-only.
serviceName.on does not work #30
Open
Description
Steps to reproduce
(First please check that this issue is not already solved as described
here)
- Tell us what broke. The more detailed the better.
The 'on' events don't seem to work using reduxified services.
Expected behavior
Tell us what should happen
When doing
const reduxServices = reduxifyServices(app, ["challenges"])
reduxServices.challenges.on("created", challenge => {
console.log("created challenge", challenge) // nothing happens.
})
I am expecting the callback function to be triggered.
Actual behavior
However, nothing happens.
However, if I do
However, if I do:
app.service("challenges").on("created", challenge => {
console.log("created challenge", challenge) // this works
})
It works.
System configuration
Tell us about the applicable parts of your setup.
Module versions (especially the part that's not working):
"feathers-client": "^2.3.0",
"feathers-redux-immutable": "^0.1.0",
"redux": "^3.7.2",
NodeJS version:
v8.1.4
Operating System:
Mac OS
Browser Version:
Chrome 60.0.3112.101
@eddyystop any ideas to what I could be doing wrong? I did not see an example of this unfortunately so I expected it to work similarly to regular service calls.