Sriamsh - Add Previous Logs preview panel to Daily Equipment Log#4655
Sriamsh - Add Previous Logs preview panel to Daily Equipment Log#4655Sriamshreddy000 wants to merge 2 commits intodevelopmentfrom
Conversation
✅ Deploy Preview for highestgoodnetwork-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Vikas-8055
left a comment
There was a problem hiding this comment.
hi sriamsh
Tested this PR locally with the backend Development branch. The "Previous Logs" collapsible panel renders correctly under the Daily Equipment Log table, shows appropriate empty state when no logs exist, and auto-updates based on selected date and project filters. Panel styling and collapse behavior work as expected.
Minor issue: Clicking Submit shows "Failed to update equipment logs" error
Hi Vikas, |
sayali-2308
left a comment
There was a problem hiding this comment.
- Checked out branch:
sriamsh_previous_logs_panel_daily_equipment - Backend: Running on
developmentbranch - Tested on: Windows, Chrome browser
- Both servers running locally (Backend: 4500, Frontend: 5173)
Note: Pre-existing CSS issues observed in Project dropdown (light background instead of dark) - not related to this PR's Previous Logs panel feature
Previous Logs preview panel successfully implemented:
- Collapsible panel appears below equipment table
- Panel collapsed by default to avoid clutter
- Displays columns: Equipment, Type, Time
- Shows empty state message when no logs available
- Auto-updates when date or project filter changes
- Styled correctly for both light and dark modes
- Helps users see previous log entries for selected date and project
Feature works as described and improves workflow by showing equipment log history, preventing duplicate entries and reducing need to navigate to other pages. All requirements met.
Hi, I found that there was a date mismatch in the code which was preventing logs from displaying correctly. I’ve fixed that and made the necessary updates to ensure the Previous Logs panel now shows the correct entries. It should now behave as expected |
There was a problem hiding this comment.
Hi Sriamsh,
I have reviewed your PR locally and the logs are visible in both the modes and work as per requirement. However as mentioned in the PR: #4701 (review) same issue is occurring here. Please fix before merge.
…bjectId, and compute historical Working/Available/Using per entry
fda4393 to
fbb9b9a
Compare
|













Description
Related PRS (if any):
To test this frontend PR you need to checkout the Development branch of backend.
Main changes explained:
How to test:
npm installandnpm startto run this PR locallyScreenshots or videos of changes: