sveltejs / sveltejs/kit

Extend remote function's refresh with an optional server push functionality

Open
#15,070 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
20.8k
Forks
2.3k
Avg merge
1d 16h
Merged PRs (30d)
156

Description

Describe the problem

i would like to have basic convex-style live updating capabilities built into remote functions. Essentially mutations to the data on the backend should actively trigger updates on the client.

Describe the proposed solution

it would be great, if there would be an optional parameter in the new remote functions, that would, if set to true, establish e.g. a websocket channel, that would push updated data to the client.

there are two use cases:

  1. There is a page with a list and a delete remote function for some items on the page. The delete function has a refresh for the list function as part of the deletion workflow, and should return updated list data. This use case seems to be covered with single-flight mutations.
  2. items in the first use case are CRUDed not only via a UI in the app, but also via an API endpoint called by external apps. Upon a mutation of the list, the updated data should be sent to the client to update the list.

Use case 2 would be catered to by this request.

Alternatives considered

built this myself

Importance

would make my life easier

Additional Information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name files, tests, or entry points. Start by locating the remote functions refresh and single-flight mutations implementation, then assess how an optional websocket-based push channel could cover updates from external API mutations; done would require a decided design and corresponding client updates.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.