Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Should we rename APIs? sangte -> atom

See original GitHub issue

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

Issue Analytics

State:
Created a year ago
Comments:7 (4 by maintainers)

Top GitHub Comments

2reactions

velopertcommented, Sep 17, 2022

Thank you for sharing your thoughts everyone!

My current plan is:

Create alias atom for sangte, useSangteState for useSangte and keep all the API name as is.

There might be some changes after getting more feedbacks from other developers later on. By the way I am planning to make a video about this library (in English) sooner or later!

2reactions

kyuncommented, Sep 12, 2022

Jotai means a state in Japanese. I guess you have already known this. From the same perspective, The name Sangte looks okay.