https://github.com/photovoltex/tauri-interop

Easily connect your rust frontend and backend without writing duplicate code.
https://github.com/photovoltex/tauri-interop

leptos rust tauri wasm

Last synced: 3 months ago
JSON representation

Easily connect your rust frontend and backend without writing duplicate code.

• Host: GitHub
• URL: https://github.com/photovoltex/tauri-interop
• Owner: photovoltex
• Created: 2023-11-25T21:40:32.000Z (about 1 year ago)
• Default Branch: main
• Last Pushed: 2024-03-24T12:53:29.000Z (10 months ago)
• Last Synced: 2024-04-25T14:01:56.099Z (9 months ago)
• Topics: leptos, rust, tauri, wasm
• Language: Rust
• Homepage:
• Size: 932 KB
• Stars: 7
• Watchers: 1
• Forks: 3
• Open Issues: 5
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Tauri-Interop

[![Latest version](https://img.shields.io/crates/v/tauri-interop.svg)](https://crates.io/crates/tauri-interop)

[![Documentation](https://docs.rs/tauri-interop/badge.svg)](https://docs.rs/tauri-interop)

![License](https://img.shields.io/crates/l/tauri-interop.svg)

This crate tries to provide a general more enjoyable experience for developing tauri apps with a rust frontend.

> tbf it is a saner approach to write the app in a mix of js + rust, because the frameworks are more mature, there are

> way more devs who have experience with js and their respective frameworks etc...

> 

> but tbh... just because something is saner, doesn't stop us from doing things differently ^ヮ^

Writing an app in a single language gives us the option of building a common crate/module which connects the backend and 

frontend. A common model itself can most of the time be easily compiled to both architectures (arch's) when the types 

are compatible with both. The commands on the other hand don't have an option to be compiled to wasm. Which means they

need to be handled manually or be called via a wrapper/helper each time.

The crates therefore provides the following features:

- generate a wasm function out of the defined tauri-command

- collect and register all defined tauri-commands

- QOL-macros to exclude multiple imports in wasm or the host architecture

- easier usage of [tauri's event feature](https://tauri.app/v1/guides/features/events/)

### Note

The library uses a resolver 2 features to allow easy inclusion without configuration. When working with virtual 

workspaces the resolver defaults to 1. In that case it is required to set the resolver manually to version 2,  

otherwise the [target specific compilation](https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#platform-specific-dependencies)

will not resolve correctly. When the wrong resolver is used, an error should state that the `Listen` trait is missing.