Sprint 2: Guard Verification & Compliance UI (Employer Panel) #194
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.
This PR implements Sprint 2 guard compliance features in the Employer Panel, enabling employers to clearly assess guard eligibility and avoid assigning guards with expired or invalid documentation.
The focus of this work is on frontend compliance logic and UX, aligned with Guard App behaviour. Due to a separate authentication/token issue currently affecting guard retrieval, mock guard data is temporarily used and clearly documented in the code. The UI and logic are fully ready to switch to real API data once resolved
Technical Notes
Frontend compliance logic is complete and API-ready
Temporary mock data (DEV_GUARDS) is used only to unblock Sprint 2 UI work
No backend or environment changes included