Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork4.6k
feat: ExportcreateReactiveFunction
#15633
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
feat: ExportcreateReactiveFunction
#15633
Uh oh!
There was an error while loading.Please reload this page.
Conversation
changeset-botbot commentedMar 28, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
|
|
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 underlyingReactiveValue
class as well (or instead)?
Uh oh!
There was an error while loading.Please reload this page.
Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>
Yeah I called that out as well -- overall I think the function is more useful (it works with |
Uh oh!
There was an error while loading.Please reload this page.
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