| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
- Implements solution for issue splitbee#87: Return errors when importing unsupported content types - Adds UnsupportedBlockError component with clear, actionable error messages - Supports databases, checkboxes, table of contents, and other unsupported blocks - Provides helpful suggestions (remove block or use react-notion-x) - Maintains backward compatibility with showUnsupportedBlockErrors prop (default: true) - Includes optional onUnsupportedBlock callback for custom error handling - Adds comprehensive CSS styling with dark mode support - Replaces silent failures with user-friendly error messages Breaking change: None - error display is enabled by default but can be disabled Fixes: splitbee#87
|
Could someone from the team kindly review and approve the pending workflows when possible? Would be great to get this merged. Thanks! ( @cball , @dvdsgl , @thmsmlr , @transitive-bullshit ).. |
Sorry, something went wrong.
|
HI |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This PR implements user-friendly error handling for unsupported block types in react-notion, addressing Issue #87.
Problem Solved
Previously, when unsupported content types (databases, checkboxes, table of contents) were encountered, the library would silently fail to render content, leaving users confused.
Solution Implemented
Files Changed
Fixes #87