Feat: Webhook monitoring#322
Draft
sarimrmalik wants to merge 15 commits into
Draft
Conversation
…dashboard into feat/webhook-monitoring
- Added new API endpoints for listing webhook deliveries, retrieving individual delivery attempts, and fetching delivery statistics. - Introduced new components for displaying webhook delivery details, including status, request/response data, and error handling. - Enhanced the OpenAPI specification to include new schemas and paths related to webhook deliveries. - Updated the dashboard layout to support navigation to webhook delivery details and statistics. These changes aim to improve the monitoring and management of webhook deliveries within the dashboard.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…w page - Removed redundant default stats range calculation in favor of a dedicated utility function. - Updated the WebhookOverviewPage to utilize the new getWebhookStatsRange function for better clarity. - Enhanced WebhookOverviewContent to accept initial range bounds as a prop, improving flexibility. - Refactored WebhookRangeSelector to handle range changes more effectively. These changes aim to streamline the management of webhook statistics and improve code maintainability.
- Replaced useRouter with Link for navigation in WebhookTableRow, enhancing accessibility and simplifying the code. - Modified WebhookNameAndUrl component to accept an href prop for direct linking. - Improved the overall structure and readability of the webhook table row component. These changes aim to streamline navigation and improve user experience in the dashboard.
- Introduced WebhookEventBadges component to visually represent webhook events in the dashboard. - Updated WebhookDetailHeader to include a badge for the webhook ID with a copy functionality. - Refactored DashboardLayoutHeader to conditionally render webhook titles based on the route. - Added ToolboxComponent to the monitoring chart for improved user interaction. These changes aim to improve the user experience by providing clearer information and better interaction options for webhook management.
sitole
reviewed
May 14, 2026
| Supabase2TeamAuth: [] | ||
| parameters: | ||
| - $ref: "#/components/parameters/webhookID" | ||
| - name: offset |
Member
There was a problem hiding this comment.
Can we use cursor listing instead?
…e schema - Enhanced GetWebhookDeliveryStatsInputSchema to include a validation rule ensuring the delivery stats range does not exceed 7 days. - Removed '30d' option from WebhookStatsRangeSchema and related components to simplify the selection options. These changes aim to improve data integrity and user experience when selecting webhook delivery statistics.
- Updated the API and OpenAPI specification to replace offset-based pagination with cursor-based pagination for listing webhook deliveries. - Modified related components and queries to support the new cursor parameter, enhancing the efficiency of data retrieval. - Improved user experience by allowing seamless navigation through delivery records with the addition of a "Load more" button. These changes aim to optimize the performance and usability of webhook delivery monitoring in the dashboard.
…t/webhook-monitoring
…omponent - Refactored WebhookDetailHeader to utilize the new IdBadge component for displaying and copying webhook IDs. - Added functionality to show the latest event timestamp and created date in a more user-friendly format. - Introduced IdBadge component to encapsulate ID display and copy functionality, improving code reusability and readability. - Updated shared index to export the new IdBadge component. These changes aim to improve the user experience in managing webhook details by providing clearer information and streamlined interactions.
- Removed the Button wrapper around the webhook name link for a cleaner presentation. - Updated the Link component to include a title attribute for better accessibility and user experience. These changes enhance the clarity and usability of the webhook settings interface.
- Updated WebhookOverviewPage to utilize new API bounds for webhook stats. - Refactored StartedAt and WebhookDetailHeader components to use the new Timestamp component for displaying date and time. - Improved stats range handling by introducing normalization and timeframe parameters. - Simplified the stats range logic in WebhookOverviewContent for better clarity and maintainability. These changes aim to improve the user experience by providing clearer timestamp displays and more robust handling of webhook statistics.
- Removed redundant header and description from the event deliveries section for a cleaner interface. - Adjusted the layout to enhance the organization of delivery status and filter input components. These changes aim to improve the visual clarity and usability of the webhook deliveries content.
…ector - Replaced normalization logic with a new function for validating webhook stats bounds. - Updated the default stats range to 'this-week' and adjusted related components to reflect this change. - Enhanced the range selector to utilize a more flexible options structure for better maintainability. These changes aim to streamline the handling of webhook statistics and improve the user experience in selecting time ranges.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.