Feature/session history #38
Merged
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
… markdown, links)
…nts, placeholder URLs)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Pull Request: Session History Implementation
This PR implements the core functionality for recording and viewing meditation session history, integrated with the user’s Solid Pod for persistent, decentralized storage.
What issue does this PR address?
Session Recording
Automatically captures start and end times for all session types (Silent, Intro, Guided).
Solid Pod Integration
Persists session data to sessions.ttl on the user’s Solid Pod using the Turtle (TTL) RDF format.
History UI
Adds a new History tab to the main application navigation, displaying past sessions in a tabular format (Date | Start | End) with refresh support.
Code Quality Improvements
Resolves linting issues related to library directives and dangling documentation comments, ensuring compliance with modern Dart and Flutter best practices.
Associated Issue
This PR addresses session recording and Solid Pod–based storage for session history.
Type of Change
✅ New feature (non-breaking change adding session history functionality)
✅ Bug fix (non-breaking change resolving analyzer and lint warnings)
How Has This Been Tested?
Automated Testing
Unit Tests
Ran dart test test/session_logic_test.dart to validate:
TTL parsing logic
Session appending behavior
Edge cases such as empty content and missing prefixes
Lint Analysis
Verified flutter analyze --fatal-infos reports no issues.
Manual Verification
Completed Silent, Intro, and Guided sessions and confirmed entries appear in the History tab.
Verified session data persists across app restarts by reading from the Solid Pod.
Tested manual refresh functionality in the History tab.
Checklist
Changes adhere to the style and coding guidelines
Self-review completed
Code is commented in non-trivial sections
No lint or analyzer errors (flutter analyze clean)
Unit tests executed and verified
Tested on:
Windows (development environment)
Finalising Steps
Merge latest dev into this branch
Resolve any merge conflicts
Add a one-line summary to CHANGELOG.md
Push final updates and request review