-
-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
app.notify not working #1795
Comments
@panaaj documentation for app.notify was added in fc9e64d but where is it implemented? |
The error message is coming from Express routing method. |
This has somehow snuck through from #1560. I have raised PR #1796 to remove it. |
Just raising a (maybe premature) flag here, but the title of #1796 is rather misleading. AFAIK app.notify has been available and working in SK for a long time. Some recent change in the code base has broken it - this isn't just a documentation issue. |
Just fired off a few tests with 2.5.0 and 2.0.0, they both throw the same error. I think you're mistaken. |
@tkurki - yes you are correct - sorry for the confusion. It seems that at some point in the distant past I created a wrapper for app that implemented the server API elements that were documented but not yet implemented and amongst these was app.notify(). Move forward five years or so and I awrote this wrapper out of use when I was recoding things into Typescript and wondered why my plugin was causing Signal K to throw an error when app.notify() was documented. Wish I had a perfect memory! My bad. |
No worries! |
Just updated to server version 2.11.0.
I have a plugin which makes a simple call:
(the notification path and plugin id are valid string values).
The call fails with:
The text was updated successfully, but these errors were encountered: