Implement Session History, Solidarity logging, and fix Windows runner… #36
+161
−44
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 Details[#19]
What issue does this PR address
This PR implements the History Tab to record and display past meditation sessions.
Each completed session captures start and end times and stores them in the user’s Solid Pod inside a sessions.json file.
Users can view session history in a table format (Date | Start | End) and refresh the data on demand.
Additionally, this PR fixes compilation and potential crash issues in the Windows runner.
Associated Issue
This PR relates to the issue:
“The history tab will record past sessions. Simple table: Date Start End. Data stored in user's POD.”
Type of Change
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
How Has This Been Tested?
The changes were verified through the following:
Verified _startTime capture and _saveSession async function in timer.dart
Tested readPod and writePod logic for storing and retrieving sessions.json
Manually reviewed the History widget DataTable, including loading and empty states
Verified Windows runner fixes in windows/runner/flutter_window.cpp to prevent null-pointer crashes
Checklist
Changes adhere to the style and coding guidelines
I have performed a self-review of my code
I have commented my code, particularly in hard-to-understand areas
The update contains no confidential information
The update has no duplicated content
No lint check errors are related to these changes (flutter analyze)
I tested the PR on the following platforms:
Android
iOS
Linux
macOS
Windows
Web