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>
* feat(log): add Builder::split to get the raw logger implementation
This function lets you split the Builder to return the raw logger implementation along the TauriPlugin to be registered. Useful to pipe the logger to other implementations such as multi_log or tauri-plugin-devtools, allowing the plugin to be used along other logging systems.
* clippy
* covector
* Use named tempfile on Windows
* append installer
* Add change file
* Fix ci
* Wrap in a folder
* Name temp dir for eaiser debugging
* format
* temp_dir
* target_os
* Document use updater_builder instead
* Update package versions and modify OS plugin
The version numbers for multiple packages have been updated in Cargo.lock. Additionally, changes were made in the OS plugin, specifically in the `index.ts` file where asynchronous function calls have been transformed into synchronous ones.
* Update package versions in Cargo.lock
Several packages in Cargo.lock have been updated to new versions. This includes "hyper", "hyper-util", "open", "serde_json", and "zerocopy" packages. Each package has had its version, checksum, and associated dependencies adjusted to reflect the latest release.
* Update OS sync functions in documentation examples
The documentation examples for `platform`, `arch`, `type`, `family`, `version`, and `exe_extension` functions have been updated. The changes are intended to better illustrate that these functions are synchronous.
2024-07-03 23:35:25 +02:00
591 changed files with 20937 additions and 8935 deletions
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.
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__`.
**Breaking change**: The permission type when using the API is now `'granted' | 'denied' | 'prompt' | 'prompt-with-rationale'` instead of `'granted' | 'denied' | 'default'` for consistency with Rust types. When using the `window.Notification` API the type is unchanged to match the Web API type.
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.