Skip to content
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

[feat][notification] Add dev mode option #2156

Open
WSH032 opened this issue Dec 6, 2024 · 1 comment
Open

[feat][notification] Add dev mode option #2156

WSH032 opened this issue Dec 6, 2024 · 1 comment
Labels
bug Something isn't working enhancement New feature or request plugin: notification

Comments

@WSH032
Copy link

WSH032 commented Dec 6, 2024

I know that the notification plugin can only work properly after installing the application via .msi or nsis. Otherwise, it can only use the identifier of other applications (such as powershell) to send notifications.

The problem here is that tauri determines whether to use dev mode by checking if the executable is in the target/ directory.

This works fine for typical Rust applications; however, when I compile it into a dynamic library for Python to call, this method fails because the executable is python in another directory.


Here is my current solution: https://github.com/WSH032/pytauri/blob/953a44fd00b1b71e3585345d23e072225124488a/example/Tauri.windows.toml

But this is not ideal because tauri-cli will raise error for such invalid identifiers.

I hope the notification plugin can add a fn dev(self, enable: bool) option to allow users to manually set dev mode.


I haven't checked the situation on Linux and macOS yet

@FabianLars
Copy link
Member

A bit more context in #1502 (and the issues linked there)

@FabianLars FabianLars added bug Something isn't working enhancement New feature or request plugin: notification labels Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request plugin: notification
Projects
None yet
Development

No branches or pull requests

2 participants