primaryAction.url doesn't seem to be working with the new notificationCenter
Hey! we started implementing novu into our system and we've been loving the ease of use so far.
After implementing a few workflows emails, and delays, we started implementing the
NotificationCenter
and we're currently running into issues with the url and other payloads from step.inApp
for some reason no matter which url i use in primaryAction.url
the button in the notification center doesn't redirect to the url, when i tried to implement a custom onClick, i don't see any of the params i pass through the return type of step.inApp
, no primaryAction.url
no someOtherParam
nothing gets to the
frontend onPrimaryActionClick
function.
Here's my return type:
Is there some way for me to debug this? i couldn't find and references for this in the documentation.
Thx for the help 🙏13 Replies
Here's my frontend code i test with 🙏
@DevRel @Support ❤️
Hey @Eden
Looking into this
@Eden
I can reproduce the issue. Thanks for reporting it.
primaryAction.url is a bug.
Let me check if we support custom data or not
someOtherParam: 'someOtherValue', // this will also not go through
@Pawan Jain First of all, thank you so much for looking into this.
I'd love to know if custom data is/will be supported soon, since it's a base requirement for us to use the
NotificationCenter
Thx again 🙏@Eden, you just advanced to level 1!
Hey @Eden
Pawel from our team created a PR for something similar to your requirement.
https://github.com/novuhq/novu/pull/6391
What do you think? it will fit into your usecase?
@Pawan Jain Looks like it'll fit, i still hope that if
primaryAction.url
is a built in feature, it will be fixed for ease of use, but for my use-case a custom data object will do the trick. 🙏Sorry for confusion, above PR is for custom data
someOtherParam: 'someOtherValue', // this will also not go through
primaryAction.url
one is a bug and will be fixed soonThe above pr fixes my need for
someOtherValue' // this will also not go through
and thank you for the update about the url, i'd appriciate your help and would love to know when i can try it and show my team.@Eden
A small update on this. This bug is now fixed in latest version
2.0.0-canary.3
of @novu/react
Correct code snippet from
@novu/framework
workflow is as below
https://docs.novu.co/sdks/framework/typescript/steps/inbox#inbox-step-output@novu/framework
latest version is 2.0.0
@Pawan Jain Thx so much, this really helps
@Pawan Jain I'm sorry to bother you again, but the bug has not been fixed as far as i'm noticing, can you please try and reproduce?
here's my updated code:
And here's my FE console.log:
Notification received {"notification":
@Pawan Jain updated my comment 🙏
@Pawan Jain Also, please lmk if i should open a new ticket for it