Gal Schlezinger

Rename to `@next-fetch/` org

1

This repo is no longer just for SWR (although it's my favorite tool). It just makes sense to make the packages have a more consistent naming scheme, so `next-swr-endpoints` and...

Allow defining an endpoint with client-side response validation

1

The idea behind this feature is to enable long-running clients to react to changes in the backend schemas. Imagine you have an endpoint that returns `{ version: 1, data: string...

The SWR API allows users to opt out of fetching by having a `null` key: ```ts useSWR(() => someCondition ? null : "/my/key", ...) ``` I think we can support...

Allow defining an endpoint without a server-side runtime parsing

1

When I asked for feedback, one person told me he does not like the fact this library forces you to declare a type in advance using `zod`, alternative libraries, or...

Idea: debouncing notifications

2

Hey! first of all - thanks for this awesome lib. Really liked that it does things "the rails way" and lets you focus on the notifications themselves. I wonder if...

Looking for collaborators

15

Hi there! Unfortunately, I don't use Rust as much as I would want. If some of you use this library and would like to get a push access to make...

It might be more performant, and because currently, it is static (you can't add attributes on the fly), HashMap doesn't provide any benefit over a `[(key, value)]` slice that being...

This project is untested, and accepting PRs makes it hard because of it. The first thing we should do before releasing v1 is to add e2e tests.

split packages

2

* `@remastered/express` for all dev/server work _cjs output_ * `@remastered/react` for all React components(?), _esm output_ * `@remastered/core`?