Skip to content

Conversation

@hrideshmg
Copy link
Member

No description provided.

Breaking Change: The manual handling of the status update streaks has
been removed in anticipation of moving the streak logic to the business
layer instead of the client.

In its place, the API will only expose a singular mutation to mark a
particular day's status update status for the member.
The streak calculation has been moved into the database layer using a
gaps-and-islands CTE. Hence streaks can now be dynamically generated
from the existing status update history data and thus the existing
streak tables are now redundant.
The project and statusupdatestreak tables are now redundant and hence
can be dropped from the database
@hrideshmg hrideshmg marked this pull request as ready for review October 6, 2025 16:07
@hrideshmg hrideshmg closed this Oct 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants