When a user quickly saves a first attribute and opens a second attribute before the first request has completed, the `$pristine` value stored for the second is removed after the API request has completed and thus, the second change is not saved. A workaround is to remove only those pristine values that were known before saving the resource.pull/4833/head
parent
f99d1a4b5d
commit
6680f94baa
Loading…
Reference in new issue