Skip to content
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

📚 Docs Feedback: _digestedNotificationId Not Documented #325

Open
1 task done
Khongchai opened this issue Nov 2, 2023 · 0 comments
Open
1 task done

📚 Docs Feedback: _digestedNotificationId Not Documented #325

Khongchai opened this issue Nov 2, 2023 · 0 comments

Comments

@Khongchai
Copy link

Duplicates

  • I have searched the existing issues

Related page

https://docs.novu.co/api-reference/notification/get-notifications

Kind of issue

Missing information

Issue description

Hi Novu team! Thank you for all your hard work. Much appreciated.

The _digestedNotificationId is missing from this page.

It is a part of the returned response's body

image

This information is actually pretty useful if one wants to find out whether their message was payload or not, so I think it should be documented. You guys are even using it here

However, one thing worth mentioning is that v1/notifications returns the property, but v1/notifications/{id} does not. The behavior might have to be aligned.

Context 🔦

I was just trying to find out an easy way to determine whether the message that I have was digested or not. While _digestedNotificationId is not very accurate, as it might mean that it's something else within the same workflow that is digested, it's better than doing response.jobs[i].digest.events > 1 where response is the response object from v1/notifications/{id}

@jainpawan21 jainpawan21 transferred this issue from novuhq/novu Nov 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant