* Make deep link optional for single instance
* Add change file
* Add deep-link feature to example
* Update plugins/deep-link/README.md
Co-authored-by: Fabian-Lars <fabianlars@fabianlars.de>
* format
* [skip ci] update readme
---------
Co-authored-by: Fabian-Lars <fabianlars@fabianlars.de>
* In the `writeFile` function, when `options.baseDir` is not set, convert `path` to URL to avoid errors caused by Chinese characters.
* fmt
* use TextEncoder
* use percent encoding
* add change file
* fmt
---------
Co-authored-by: Lucas Nogueira <lucas@tauri.studio>
* feat(deep-link): implement getCurrent on Windows/Linux
checks std::env::args() on initialization, also includes integration with the single-instance plugin
* fmt
* update docs, fix event
* add register_all function
* expose api
* be nicer on docs, clippy
* chore(ios): consolidate optional argument standard
mark all optional iOS arguments as `var <name>: Type?`, following the pattern described in the documentation: https://v2.tauri.app/develop/plugins/develop-mobile/#ios
* chore: add missing Info.plist to example
* chore: adjust prettier config, .gitignore and use taplo to format toml files
This brings the plugins-workspace repository to the same code style of the main tauri repo
* format toml
* ignore examples gen dir
* add .vscode/extensions.json
* remove packageManager field
* fmt
* fix audit
* taplo ignore permissions autogenerated files
* remove create dummy dist
* fix prettier workflow
* install fmt in prettier workflow
---------
Co-authored-by: Lucas Nogueira <lucas@tauri.app>
The Android and iOS support introduced on #1011 is not really supported - the Tauri path API correctly resolves the cache directory on mobile, and we can access those directly using Rust code.
This is a breaking change because we no longer uses the same directory to store the files - app_cache_dir returns a different location
* fix(updater): linux not retaining AppImage permissions, enhance tests
- adds a test for migration from v1 to v2
- extends the existing integration test to actually verify if the app was updated
* remove test framework
* fix macos test
* fix windows
* wait on windows
* fix wix
* typo
* fmt
* install webkit2gtk-4.0 on ci
* fix npm command on windows
* fix test on windows
* ubuntu-22.04
---------
Co-authored-by: Tillmann <28728469+tweidinger@users.noreply.github.com>
* fix: use `_` as word boundary in IIFE var names
* Revert "fix: use `_` as word boundary in IIFE var names"
This reverts commit 396ed3fa56.
* Reapply "fix: use `_` as word boundary in IIFE var names"
This reverts commit f31de7dab3.
* init geolocation plugin
* ios impl (w/o js api)
* generate ts api
* use newer tauri commit
* add temporary postinstall
* include src in files
* guest-js
* just ship dist-js for now
* fix watcher
* fix android compile error
* fix android build for real
* fix heading type
* initial getCurrentPosition android impl (wip)
* prevent panics if errors (strings) are sent over the channel
* Add android watchPosition implementation
* init haptics plugin (android)
* ios and new apis (ANDROID IS LIKELY BROKEN - MAY NOT EVEN COMPILE)
* use tauri-specta that accounts for raw fn arg idents
* add complete android support (it's not working great due to random soft-/hardware support)
* fix(haptics): Fix the NotificationFeedbackType::Success and Version (#1)
* Fix success feedback and version
* Apply suggestions from code review
* Update package.json
---------
Co-authored-by: Fabian-Lars <118197967+FabianLars-crabnebula@users.noreply.github.com>
* android: improve permission callback handling
* keep track of ongoing perms requests
* rebuild
* license headers
* rm sqlite feat
* fmt
* what diff u talkin bout?
* ignore dist-js again
* fix audits
* dedupe api.js
* clippy
* changefiles
* readmes
* clean up todos
* rm dsstore
* rm wrong feats
* mirror
* covector
* rebuild
* ios requires the wry feature
* lint
* update lock
---------
Co-authored-by: fabianlars <fabianlars@fabianlars.de>
Co-authored-by: Brendan Allan <brendonovich@outlook.com>
Co-authored-by: Naman Garg <155433377+naman-crabnebula@users.noreply.github.com>
Co-authored-by: Lucas Nogueira <lucas@crabnebula.dev>
Use `PermissionState` from the `tauri` crate, which now also includes a "prompt with rationale" variant for Android (returned when your app must explain to the user why it needs the permission).
**Breaking change:** Removed the `default-tls` feature flag. The `rustls-tls`, `http2`, `macos-system-configuration`, and `charset` feature flags are now enabled by default.
Fixed an issue that caused the `notification` plugin's initialization script to cause the WebView on Windows to throw a `STATUS_ACCESS_VIOLATION` error on remote websites.
Refactored APIs to introduce new pressed and released events:
- Added `ShortcutEvent` and `ShortcutState` types in Rust.
- Changed the handler function passed to `GlobalShortcut::on_shortcut`, `GlobalShortcut::on_all_shortcuts` and `Builder::with_handler` to take a 3rd argument of type `ShortcutEvent`.
- Added `ShortcutEvent` interface in JS.
- Changed `ShortcutHandler` type alias (which affects the JS `register` and `registerAll` APIs) to take `ShortcutEvent` instead of a string.
**Breaking change** Refactored the plugin Rust APIs for better DX and flexibility:
- Changed `Builder::with_handler` to be a method instead of a static method, it will also be triggered for any and all shortcuts even if the shortcut is registered through JS.
- Added `Builder::with_shortcut` and `Builder::with_shortcuts` to register shortcuts on the plugin builder.
- Added `on_shortcut` and `on_all_shortcuts` to register shortcuts with a handler.
Fixed an issue that caused multi-word IIFE names to not be formatted correctly. For example the `barcode-scanner` was defined as `window.__TAURI_PLUGIN_CLIPBOARDMANAGER__` instead of `window.__TAURI_PLUGIN_CLIPBOARD_MANAGER__`.
Use no default features on tauri for all plugins so that consumers can use `default-features = false` on tauri, note that this will still enable wry feature on iOS
The notification body is now optional on iOS to match the other platforms.
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.