jaredpalmer / jaredpalmer/formik

After submitting a form the isSubmitting property is automatically set back to false without calling setSubmitting()

Open
#1,985 3 comments 1 reaction 0 assignees View on GitHub
stale
Dominant language
TypeScript
Stars
34.3k
Forks
2.8k
PR merge metrics
No merged PRs in 30d

Description

## 🐛 Bug report

### Current Behavior

After submitting a form the isSubmitting property is automatically set back to false without calling setSubmitting(). Note how fields and buttons are disabled after clicking submit, but then become reenabled.
![isSubmitting](https://user-images.githubusercontent.com/29407020/68047456-adf29f00-fc9b-11e9-9f51-ed999ebb6968.gif)

### Expected behavior

isSubmitting should remain true until developer calls `setSubmitting(true)`

### Your environment

| Software | Version(s) |
| ---------------- | ---------- |
| Formik | 2.0.3
| React | 16.11.0
| Browser | Chrome
| npm/Yarn | NPM
| Operating System | Windows

Contributor guide

Open the contributing guide

Research direction

No source file or test is named. Start by reproducing the submission behavior with Formik 2.0.3 and React 16.11.0, then trace the submission state transition; done means isSubmitting stays true until the developer calls setSubmitting().

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.