Multi-tenant revenue: caching, rounding, timezone - #136
Open
harry3098 wants to merge 1 commit into
Open
Conversation
Backend: include tenant_id in cache keys (cache.py) to avoid cross-tenant collisions; return total_revenue as a rounded Decimal string in dashboard API (dashboard.py) using ROUND_HALF_UP for consistent monetary formatting. Reservations service (reservations.py) updated signature to accept tenant_id and sketched timezone-aware start/end datetimes (uses ZoneInfo) to ensure month boundaries respect property timezone. Frontend: make Dashboard tenant-aware (AuthContext) and filter properties by tenant; RevenueSummary improved formatting, typing and uses simulatedTenant when calling SecureAPI. These changes improve multi-tenancy correctness, monetary precision, and timezone handling.
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
1 participant
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.
Backend: include tenant_id in cache keys (cache.py) to avoid cross-tenant collisions; return total_revenue as a rounded Decimal string in dashboard API (dashboard.py) using ROUND_HALF_UP for consistent monetary formatting. Reservations service (reservations.py) updated signature to accept tenant_id and sketched timezone-aware start/end datetimes (uses ZoneInfo) to ensure month boundaries respect property timezone. Frontend: make Dashboard tenant-aware (AuthContext) and filter properties by tenant; RevenueSummary improved formatting, typing and uses simulatedTenant when calling SecureAPI. These changes improve multi-tenancy correctness, monetary precision, and timezone handling.