Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent Reactivity Terminology #3512

Open
ealmloff opened this issue Jan 7, 2025 · 0 comments
Open

Inconsistent Reactivity Terminology #3512

ealmloff opened this issue Jan 7, 2025 · 0 comments
Labels
documentation Improvements or additions to documentation tweak Small changes to improve experience

Comments

@ealmloff
Copy link
Member

ealmloff commented Jan 7, 2025

Reactive Terminology

When referencing reactivity in the guide and inline docs, we haven't been very consistent with terminology. Recently I have been trying to switch to using two different terms for values in reactive code:

  1. Tracked values are values that track when they have been read. They will add themselves as dependencies to reactive hooks and automatically rerun any reactive hooks that subscribe to them when they are changed. Eg. Signal, ReadOnlySignal, Memo, and Resource are all tracked values, but Effect is not
  1. Reactive hooks are hooks that keep track of dependencies and rerun when the tracked values that are read inside of them change. Eg. use_memo, use_resource, and use_effect are all reactive hooks, but use_signal is not

It might make sense to switch the two since that seems to align more closely with other frameworks people could be familiar with

Places where we refer to tracked values as reactive today:

@ealmloff ealmloff added documentation Improvements or additions to documentation tweak Small changes to improve experience labels Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation tweak Small changes to improve experience
Projects
None yet
Development

No branches or pull requests

1 participant