feat: add nightly session notes#104
Open
kilo-WATT wants to merge 1 commit into
Open
Conversation
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.
Summary
Adds simple plain-text notes for SleepLab session/night detail pages.
Users can now add, edit, view, and clear an optional note for a sleep session/night. Notes are stored on the existing
sessionstable with a nullablenotecolumn.Because SleepLab already treats
user_id + folder_dateas the nightly boundary, saving a note updates all session rows for that same user/night so multi-block nights stay consistent.Changes
018_add_session_note.sqlnotePUT /sessions/{session_id}/noteSessionDetail.tsxScreenshot
Notes section on the session detail page:
Validation
uv run python scripts\check_migrations.pypasseduv run pytest -qpassed available tests:37 passed, 74 skippednpm run testinfrontendpassed:6 passednpm run buildinfrontendpassednpm run lintstill has pre-existing repo-wide lint failures unrelated to this PR