-
Notifications
You must be signed in to change notification settings - Fork 0
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
"Sign" form #76
"Sign" form #76
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
couple formatting questions w this part
- should the button to sign this form be grayed out or blue? I think it'd make sense for it to be colored so it indicates I need to sign it but also haven't looked at the hi-fis for what this is supposed to look like
- alignment on the approve button looks wonky, should it right-align with the end of the "already signed" text?
- is "already signed" the phrasing we want, or would something simpler like just "signed" make more sense?
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.
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.
lgtm🚀
Description/Problem
Closes story
Support signing a form.
Solution
Form signing
Dependencies
[ ] This PR adds new dependencies
Testing
Please describe how you tested this PR (manually and/or automatically)
Provide instructions so we can reproduce, and include screenshots of UI changes.