Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

244 feature add signature input in create form template flow #272

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Gayatri-K26
Copy link
Contributor

Description

  • Added handleSetSignature logic
  • Added the button for it
  • Added the signature icon

Motivation and Context

Allows users creating a form template should be able to add signature input onto the PDF for a specific signature group

Closes #244

How has this been tested?

Screenshots (if appropriate):

image

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@Gayatri-K26 Gayatri-K26 linked an issue Feb 2, 2025 that may be closed by this pull request
1 task
Copy link

vercel bot commented Feb 2, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
mfa-form-automator ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 2, 2025 8:58pm

@@ -0,0 +1,11 @@
/*
Warnings:
Copy link
Collaborator

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

@@ -133,6 +134,24 @@ export const FormEditor = ({
}
};

const handleSetSignature = () => {
const newFieldId = uuidv4();
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@@ -233,6 +252,23 @@ export const FormEditor = ({
>
<div>{TextIcon}</div>
</Button>

<Button
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Collaborator

@kaiyangzheng kaiyangzheng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left some comments in the PR.

A few more things to add:

  • We shouldn't have a package-lock.json - this only happens if you use npm install install of yarn install I believe
  • There have been a good amount of updates since this PR went up (my bad) but I would pull from main and resolve any merge conflicts before updating the PR
  • A good example to look at would be Donny's PR adding checkboxes: Added checkbox and delete functionality  #298

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[FEATURE] Add signature input in create form template flow
2 participants