Skip to content

useParcelForm Request state
Compare
Choose a tag to compare
@dxinteractive dxinteractive released this 19 Jun 04:31
· 168 commits to master since this release
v0.23.0
6334e83

Addresses a missing piece of #181

react-dataparcels

  • BREAKING CHANGE ParcelBufferControl class removed. useParcelBuffer, ParcelBoundary and useParcelForm all now return an identically shaped object in its place. This requires no code changes if you are not using the ParcelBufferControl named export.
  • Added request state info to useParcelForm #181
    • useParcelForm.onChange can already deal with promises and can handle what happens when they resolve and reject. Not passing the current state of the promise out of the hook would lead to people having to wrap their promises in something that can keep state based off of each promise,
      so much better to include that functionality natively and have it test covered and standardised.
    • You probably wouldnt bother using it if you have some other thing like enty or async data stored in redux
Assets 2