Chore/frontend/mock form page #112
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
| <Sidebar /> | ||
|
|
||
| <main className="flex-1 h-full flex flex-col"> | ||
| <div className="rounded-2xl bg-white shadow-sm ring-1 ring-black/5 h-full flex flex-col"> |
There was a problem hiding this comment.
Could we put space-y-4 here?
…ment Enable local development without external Intania Auth dependency by implementing DEV_MODE environment variable that mocks authentication with configurable user roles (admin/esc/student).
feat/mock-auth
FaiiFaiipuipui
force-pushed
the
chore/frontend/mock-form-page
branch
from
c6e75d2 to
653fdab
Compare
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.
Description
Prepare frontend for Phase3.1 in Gendoc
New mock pages for form and document status:
DocumentStatusMockPageandGenDocMockPagepages, which serve as mock implementations for document status and document generation forms, utilizing the new component system. (apps/web/src/app/documentstatusmock/page.tsx,apps/web/src/app/gendocformmock/page.tsx) [1] [2]Form field rendering architecture:
FormQuestioncomponent that routes rendering to specialized field components based on field type, supporting types like string, date, tel, timerange, estimate-people, object, and fallback for unsupported types. (apps/web/src/components/gendocformcomponents/FormQuestion.tsx)FormQuestionString,FormQuestionDate,FormQuestionEstimatePeople, andFormQuestionObject, each handling their respective input types and constraints, with design notes for further improvements. (apps/web/src/components/gendocformcomponents/FormQuestionString.tsx,FormQuestionDate.tsx,FormQuestionEstimatePeople.tsx,FormQuestionObject.tsx) [1] [2] [3] [4]FallBackComponentto gracefully handle unsupported or unimplemented field types, improving robustness. (apps/web/src/components/gendocformcomponents/FallBackComponent.tsx)Document status visualization:
DocumentStatuscomponent that visually represents the document approval workflow, including stage coloring and sub-status indicators (e.g., rejected, processing, approved) for stage 3. (apps/web/src/components/gendocformcomponents/DocumentStatus.tsx)These changes lay the groundwork for a scalable, maintainable form system and provide clear UI feedback for document status and form input handling.