244 feature add signature input in create form template flow #272
There are no files selected for viewing
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| /* | ||
| Warnings: | ||
|
|
||
| - You are about to drop the column `employeeId` on the `Signature` table. All the data in the column will be lost. | ||
|
|
||
| */ | ||
| -- DropForeignKey | ||
| ALTER TABLE "Signature" DROP CONSTRAINT "Signature_employeeId_fkey"; | ||
|
|
||
| -- AlterTable | ||
| ALTER TABLE "Signature" DROP COLUMN "employeeId"; | ||
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,7 +1,7 @@ | ||
| import { useRef, useState } from 'react'; | ||
| import { Document, Page, pdfjs } from 'react-pdf'; | ||
| import { Box, Text, Button } from '@chakra-ui/react'; | ||
| import { TextIcon, PlusSign, SignatureIcon } from 'apps/web/src/static/icons'; | ||
| import { DraggableData, DraggableEvent } from 'react-draggable'; | ||
| import PagingControl from './PagingControl'; | ||
| import { v4 as uuidv4 } from 'uuid'; | ||
|
|
@@ -50,6 +50,7 @@ export const FormEditor = ({ | |
| const [totalPages, setTotalPages] = useState(0); | ||
| const documentRef = useRef<HTMLDivElement>(null); | ||
| const [groupNum, setGroupNum] = useState(fieldGroups.size); | ||
| const [signatureFieldId, setSignatureFieldId] = useState<string | null>(null); | ||
|
|
||
| //colors for group buttons: colors[0] = border/text color, colors[1] = background color | ||
| const groupColors = [ | ||
|
|
@@ -133,6 +134,24 @@ export const FormEditor = ({ | |
| } | ||
| }; | ||
|
|
||
| const handleSetSignature = () => { | ||
| const newFieldId = uuidv4(); | ||
|
There was a problem hiding this comment. This logic is valid, I would create a new component other than DraggableText to represent signatures, especially with the new designs for signature boxes: https://www.figma.com/design/xTNJRHyohsIf714Ba1eWFY/Hi-fi-Wireframes?node-id=5741-1908&m=dev |
||
| setSignatureFieldId(newFieldId); | ||
| setFormFields({ | ||
| ...formFields, | ||
| [pageNum]: new Map([ | ||
| ...formFields[pageNum], | ||
| [ | ||
| newFieldId, | ||
| { | ||
| position: { x: 0, y: 0, width: 150, height: 50 }, | ||
| groupId: currentGroup, | ||
| }, | ||
| ], | ||
| ]), | ||
| }); | ||
| }; | ||
|
|
||
| return ( | ||
| <Box | ||
| background="white" | ||
|
|
@@ -233,6 +252,23 @@ export const FormEditor = ({ | |
| > | ||
| <div>{TextIcon}</div> | ||
| </Button> | ||
|
|
||
| <Button | ||
|
There was a problem hiding this comment. Selecting this should disable the text box input and make the background of the signature button darker. Not sure if I'm looking at it wrong, but the screenshots look off, as the Text button is still selected. |
||
| position="relative" | ||
| width="40px" | ||
| height="40px" | ||
| backgroundColor="#1367EA" | ||
| borderRadius="4px" | ||
| display="flex" | ||
| justifyContent="center" | ||
| alignItems="center" | ||
| isDisabled={fieldGroups.size == 0 || disableEdit} | ||
| border="1px solid #1367EA" | ||
| onClick={() => handleSetSignature()} | ||
| > | ||
| <div>{SignatureIcon}</div> | ||
| </Button> | ||
|
|
||
| </Box> | ||
| <Box | ||
| height="474px" | ||
|
|
||
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We shouldn't have to make a new migration - i would delete this folder. I think this comes from running yarn prisma migrate dev, which automatically generates a new migration. I think yarn prisma migrate reset to run the migrations + seedings should be fine