velopert / sangte Goto Github PK

By default, state is removed when no component is referencing it.
Therefore, state can be lost unexpectedly when the state is used from page A and B, and user redirects the page from A to B.

To fix this issue, these options should be implemented in config.

cleanupTimeout: the state should be removed after this timeout. by default, set this to 1000,
preserve: this option will preserve the state even when the state is not referenced from any component.

As a Korean, I really liked the name sangte since it just makes sense.

However, after putting myself into foreign developers' shoes, I thought that they might not like it because they are not used to this word.

Thus, I am planning to change the name as below. I need some feedback! Should I go for it? Or stick with the current naming?

sangte -> atom
useSangte -> useAtom
useSangteActions -> useAtomActions
useSangteValue -> useAtomValue
useSetSangte -> useSetAtom
useSangteStore -> useAtomStore
useSangteCallback -> useAtomCallback
useResetSangte -> useResetAtom
useResetAllSangte -> useResetAllAtoms