Read/Write outside of component about recoil

[atulmy]

I was wondering same. My use case was more around the user login state from localStorage. I ended up doing this:

Redux (inside /src/index.js):

// User Authentication
const token = window.localStorage.getItem('token')
if (token && token !== 'undefined' && token !== '') {
  const user = JSON.parse(window.localStorage.getItem('user'))
  if (user) {
    loginSetUserLocalStorage(token, user)
    store.dispatch(loginSetUser(token, user))
  }
}

Recoil (inside /src/user/api/state.js):

const userAuthDefault = {
  isAuthenticated: false,
  user: null
}

// on page load
// try to get user token and details from localStorage
const token = window.localStorage.getItem('token')
if (token && token !== 'undefined' && token !== '') {
  const user = JSON.parse(window.localStorage.getItem('user'))

  if (user) {
    userAuthDefault.isAuthenticated = true
    userAuthDefault.user = user
  }
}

// auth
export const userAuth = atom({
  key: 'userAuth',
  default: userAuthDefault
})

Hope this will help for some use cases.

[davidmccabe]

It's not currently possible. Recoil state is not global but exists within a particular React context, and there is also no "current" state, just the most recently committed state from the point of view of a particular component.

If you tell me what you actually need to do then I can suggest how to do it.

[JesperLekland]

We have a pretty big brownfield app, meaning that we would need to gradually migrate from our current solution of Redux (which have the feature in question, and which we use to a certain extent). We also have a few "external" modules that are agnostic to the component context but still have access to the state, e.g an API module, a deep-linking module etc.

[keene-dalveytech]

It looks like an ugly way to write it