Repository navigation
Conversation
…thly summaries This change hardens the dashboard flow across the backend and frontend by enforcing tenant-aware access controls and improving data consistency for property and revenue queries. Backend updates: - tighten tenant resolution and property access checks to prevent cross-tenant data leakage - scope dashboard property listings and summary queries to the active tenant - ensure monthly revenue aggregation respects local month boundaries and property ownership - validate single-currency totals for property-level reservation summaries - clear and refresh tenant-scoped cache entries when dashboard data changes - add integration coverage for property scoping, month-boundary logic, and cross-tenant access rejection Frontend updates: - load dashboard properties dynamically from the authenticated API instead of relying on static mock data - add a month selector and default-to-latest-month behavior - pass the selected month through the summary component for accurate revenue filtering - show user-facing errors when the dashboard data cannot be loaded Tests: - add end-to-end integration checks for seeded tenant data, cross-tenant isolation, and summary correctness across multiple months This keeps the dashboard aligned with the tenant model, prevents unauthorized data access, and verifies the behavior with real API-level regression tests.
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.
This change hardens the dashboard flow across the backend and frontend by enforcing tenant-aware access controls and improving data consistency for property and revenue queries.
Backend updates:
Frontend updates:
Tests:
This keeps the dashboard aligned with the tenant model, prevents unauthorized data access, and verifies the behavior with real API-level regression tests.