We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hey so this is just an idea to make life a tiny bit easier when updating versions of TunnlTo.
Automaticlly get the Version of TunnlTo for the UI display on the settings page (src\components\containers\Settings.tsx) by adding
src\components\containers\Settings.tsx
import { getVersion } from '@tauri-apps/api/app' const appVersion = await getVersion();
and changing
<p className="text-xs text-gray-600 pt-2"> TunnlTo 1.0.6 <br /> WireSock {wiresockInstallDetails?.version} </p>
to
<p className="text-xs text-gray-600 pt-2"> TunnlTo {appVersion} <br /> WireSock {wiresockInstallDetails?.version} </p>
only issue I see is you would need to fix the "Top-level await" error it will give you after by adding
build: { target: "es2022" }
to vite.config.ts
vite.config.ts
but just an idea to make it so whatever the tauri.conf.json file says for the version is what it will show on the settings page UI
tauri.conf.json
The text was updated successfully, but these errors were encountered:
Thanks for this. I've implemented something similar in version 1.0.7
Sorry, something went wrong.
No branches or pull requests
Hey so this is just an idea to make life a tiny bit easier when updating versions of TunnlTo.
Automaticlly get the Version of TunnlTo for the UI display on the settings page (
src\components\containers\Settings.tsx
) by addingand changing
to
only issue I see is you would need to fix the "Top-level await" error it will give you after by adding
to
vite.config.ts
but just an idea to make it so whatever the
tauri.conf.json
file says for the version is what it will show on the settings page UIThe text was updated successfully, but these errors were encountered: