[Notion] fix for new pages

[andrewjschuang]

WHY

Summary by CodeRabbit

• New Features
  • Updated the includeNewPages property to emit events for newly created pages by default.
• Bug Fixes
  • Improved error handling for accessing property values in the updated-page source module.
• Chores
  • Updated package versions for @pipedream/notion and notion-updated-page source module.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
docs-v2	⬜️ Ignored (Inspect)			Sep 27, 2024 0:44am
pipedream-docs	⬜️ Ignored (Inspect)			Sep 27, 2024 0:44am
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Sep 27, 2024 0:44am

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces updates to the @pipedream/notion package, incrementing its version from 0.1.23 to 0.1.24. Additionally, the notion-updated-page source module sees its version updated from 0.0.18 to 0.0.19, with changes to the includeNewPages property, including an updated description and a new default value of true. A nullish coalescing operator is also introduced to enhance the safety of property access.

Changes

File	Change Summary
components/notion/package.json	Updated @pipedream/notion version from 0.1.23 to 0.1.24.
components/notion/sources/updated-page.mjs	Updated version from 0.0.18 to 0.0.19, modified includeNewPages description and default value from false to true, and added nullish coalescing operator in property access.

Possibly related PRs

• Notion - updated page trigger fix #13972: Updates the version of the @pipedream/notion package in package.json, changing it from 0.1.23 to 0.1.24.
• Notion - updated-page source improvements #14045: Updates the version of the @pipedream/notion package in package.json, reflecting a version change from 0.1.21 to 0.1.22.
• [Notion] updated page trigger fix #14116: Updates the version of the @pipedream/notion package in package.json, changing it from 0.1.22 to 0.1.23.

Suggested reviewers

• luancazarine
• jcortes

🐇 In the garden of code, I hop and play,
With versions updated, we brighten the day.
New pages now dance, as events take flight,
In the world of Notion, everything feels right!
So let’s celebrate with joy and cheer,
For every small change brings us near! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[andrewjschuang]

Related to #13773