-
Notifications
You must be signed in to change notification settings - Fork 308
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
Should FileResponse
be #[non_exhaustive]
?
#1623
Labels
Comments
FileResponse was exported in #837 without discussion about |
FabianLars
added
question
Further information is requested
plugin: fs
Includes former "fs-extra" and "fs-watch" plugins
labels
Aug 3, 2024
This is about |
whoops |
FabianLars
added
plugin: dialog
and removed
plugin: fs
Includes former "fs-extra" and "fs-watch" plugins
labels
Aug 5, 2024
amrbashir
added a commit
that referenced
this issue
Aug 13, 2024
Sir-Thom
pushed a commit
to Sir-Thom/plugins-workspace
that referenced
this issue
Oct 22, 2024
…apps#1660) * recator(dialog): mark `FileResponse` as `#[non_exhaustive]` closes tauri-apps#1623 * change file
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently
tauri_plugin_dialog::FileResponse
is not#[non_exhaustive]
but this means adding fields totauri_plugin_dialog::FileResponse
is braking changes.Is this fine?
The text was updated successfully, but these errors were encountered: