Skip to content

fix broken tauri client #346

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

Closed
wants to merge 1 commit into from
Closed

fix broken tauri client #346

wants to merge 1 commit into from

Conversation

sheason2019
Copy link

create a legacy tauri transport class to make legacy typescript client declaration syntax just work.

// legacy client code running with rspc version 0.4.1
import { ProceduresLegacy } from "../bindings";
import { TauriTransport_Legacy } from "@rspc/tauri/legacy";

export const client = createClient<ProceduresLegacy>({
  transport: new TauriTransport_Legacy(),
});

export const queryClient = new QueryClient({
  defaultOptions: {
    queries: {
      retry: false,
    },
  },
});

export const rspc = createReactQueryHooks<ProceduresLegacy>();

Copy link

vercel bot commented Feb 18, 2025

@sheason2019 is attempting to deploy a commit to the Oscar Beaumont Team on Vercel.

A member of the Team first needs to authorize it.

@oscartbeaumont
Copy link
Member

I recon TauriTransport_Legacy should be renamed and exported from the root module like it previously was. Although we started work on the new client it's not ready and publically so we probally shouldn't call it legacy.

Thanks for this PR!

@sheason2019
Copy link
Author

Sorry for my late reply. Now the TauriTransport class for the v0.4 rspc backend will replace the old one.

@sheason2019 sheason2019 closed this Apr 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants