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

Form inputs without shouldSaveDraft don't update their value and submit stale data #8567

Closed
luacmartins opened this issue Apr 8, 2022 · 1 comment
Assignees
Labels
Engineering Reviewing Has a PR in review Weekly KSv2

Comments

@luacmartins
Copy link
Contributor

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. Run npm run storybook
  2. Update the value of an input without the shouldSaveDraft param, e.g. Account number in the default story.
  3. Submit the form and verify that the value submitted is stale

Expected Result:

The value should be updated and submitted correctly.

Actual Result:

Value updates on the UI, but the submitted value is stale.

Workaround:

None.

Platform:

  • Web
  • iOS
  • Android
  • Desktop App
  • Mobile Web

Version Number:
Reproducible in staging?:
Reproducible in production?:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:

View all open jobs on GitHub

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Engineering Reviewing Has a PR in review Weekly KSv2
Projects
None yet
Development

No branches or pull requests

1 participant