feat: Options fabric

[finom]

I'm integrating tRPC-like feature that would help to initiate useQuery etc requests by building list of options.

For example:

handler.queryOptions = (input, opts) => {
      const queryKey = handler.queryKey();
      return {
        queryFn: async ({ client }) => {
          const result = await handler(input);
          if (Symbol.asyncIterator in result) {
            void (async () => {
              for await (const chunk of result) {
                client.setQueryData(queryKey, (data: unknown[]) => [...data, chunk]);
              }
            })();

            return [];
          }

          return result;
        },
        queryKey,
        ...opts,
      };
    }

// it's typed separately in another file
//...
 queryOptions<R>(
    input?: Prettify<StaticMethodInput<T> & StaticMethodOptions<T, OPTS, STREAM, R, VovkDefaultFetcherOptions<OPTS>>>,
    opts?: Partial<Omit<UseQueryOptions<Awaited<ClientMethodReturn<T, STREAM, R>>, HttpException>, 'queryFn'>>
  ): UseQueryOptions<
    Awaited<ClientMethodReturn<T, STREAM, R>> extends VovkStreamAsyncIterable<infer U>
      ? U[]
      : Awaited<ClientMethodReturn<T, STREAM, R>>,
    HttpException
  >;
// ...

There is nothing specific to say about the example, except of that I need to hack into the built-in types of react-query. queryOptions wasn't too hard to do, mutationOptions was a bit harder, and I struggled a lot creating infiniteQueryOptions, so I decided to skip its implementation for now.

I'd like to request a feature that would help integrating "get options" to any library. I don't have a design proposal (I'm not a big specialist of rect-query, but would be glad to discuss), but roughly saying, it would be great to have a fabric that creates these functions. Something like:

const getQueryOptions = createQueryOptionsFabric<TInput>({ queryFn });
useQuery(getQueryOptions(input, otherOptions));

Of course, an additional layer of abstraction is quite bulky, but might help a lot in building client libraries that perform requests over applicable protocols.

Maybe I missed something and there is already a feature of this kind? Thanks.