Question: Fetch atoms/selectors via "key"?

According to the docs, each atom/selector need to be given a unique key. Is it possible/planned to get an atom/selector by this key? If not, is there a way the library could generate a unique key without forcing the user to provide it?

// ...somewhere in the app...
const tempFahrenheit = atom({
  key: 'tempFahrenheit',
  default: 32,
});
//

const [tempF, setTempF] = useRecoilState('tempFahrenheit');

Just trying to get a better understanding of the library. Thanks 😃

[drarmstr]

We’ve discussed this internally. There were some proposals to add Recoil “zones/contexts”, which would help solve the key namespace concern and help with composability. Though, this isn’t the highest priority at the moment. In the meantime, we use conventions for namespacing keys, e.g. 'Module/Key'.

No current plans to allow non-opaque strings as atom/selector handles in the API. Generally we want to enforce that you’re actually working with the same shared atom/selector, provide protection from string typos, etc. It has worked pretty well to export shared atoms/selectors from shared modules that can be imported from the components or selectors that need them.

[ShanonJackson]

Don’t like fetch by key because could lead to weird behaviour where the atom itself isn’t included in the bundle because no-one imports it because it’s just being referenced by key name.