-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
🐛 Fixed missing enable_comment_notifications property in member serializer #23146
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
base: main
Are you sure you want to change the base?
🐛 Fixed missing enable_comment_notifications property in member serializer #23146
Conversation
…lizer closes TryGhost#22858 By adding in the `enable_comment_notifications` property into both the `serializeMember` function and the SerializedMember type definition, this enables it to be correctly be presented in the webhook payload.
WalkthroughThe changes introduce a new boolean property, Assessment against linked issues
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (3)
🧰 Additional context used🧬 Code Graph Analysis (1)ghost/core/test/utils/fixtures/data-generator.js (2)
🔇 Additional comments (4)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
fixes #22858
The
enable_comment_notifications
field isn't currently included in theserializeMember
function of the members output serializer. This prevents automations from being able to utilise this value.This small change adds in that field (as well as adding it in the SerializedMember type definition) which enables it to be available in the webhook payload which in turns allows automations to utilise it.
I don't forsee any particular unwanted side-effects as the field is non-nullable in the database and therefore always present but I welcome more thoughts on this.
I've added a small test to demonstrate the property is included as expected in the read response but I'd like to add more as I explore further into the codebase.