-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
feat: Export createReactiveFunction
#15633
base: main
Are you sure you want to change the base?
feat: Export createReactiveFunction
#15633
Conversation
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we expose the underlying ReactiveValue
class as well (or instead)?
Co-authored-by: Simon H <[email protected]>
Yeah I called that out as well -- overall I think the function is more useful (it works with |
TODO:
ReactiveValue
? IMO no, as this seems like the better way to do this, especially when combined with$derived.by
, but I'm not completely attached to that opinionBefore submitting the PR, please make sure you do the following
feat:
,fix:
,chore:
, ordocs:
.packages/svelte/src
, add a changeset (npx changeset
).Tests and linting
pnpm test
and lint the project withpnpm lint