setting an atom with a promise results in `deleting atomState with read promise` error

I put together an example here:

https://github.com/zcaudate/js-blessed.store-test

but basically I’m getting an error when using atoms with Suspense.

I’d like to be able to have an atom that is initialised with nil, can have a promise resolving to some data and then be reset back to nil.

So in the example, the atom’s initial value is null. createRecord is basically create atom with some metadata stuffed into it:

Then I set the atom’s value to a promise (which resolves after a time out) and it produces this error in the suspense element:

// React will try to recreate this component tree from scratch using the error boundary you provided, Debug.
[Bug] deleting atomState with read promise {
  toString: [Function: toString],
  init: null,
  read: [Function (anonymous)],
  write: [Function (anonymous)],
  id: 'js-blessed.store-test.main/UserData',
  section: 'js-blessed.store-test.main/User'
}

This is a bug or a feature of atoms in jotai and if it’s a feature, how do I implement a resettable atom with a promise?

[zcaudate]

thanks for your help!

[zcaudate]

okay. this actually works on the dom:

https://codesandbox.io/s/react-typescript-forked-813p1?file=/src/App.tsx

It must be an issue with the react-blessed renderer.