forked from quasarframework/quasar
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Updated Laotian translation #3
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…d PWA update to force re-download all assets Due to how Rollup builds the assets (through Vite), when you change any of your script source files (.js) this will also change the hash part of (almost) ALL .js files (ex: `454d87bd` in `assets/index.454d87bd.js`). The revision number of all assets will get changed in your service worker file and this means that when PWA updates it will re-download ALL your assets again. What a waste of bandwidth and such a longer time to get the PWA updated! By default, Quasar CLI configures Vite & Rollup to build all filenames **without the hash part** to avoid the scenario above.
Co-authored-by: Yusuf Kandemir <[email protected]>
Co-authored-by: Yusuf Kandemir <[email protected]> Co-authored-by: Patrick Black <[email protected]>
Use apksigner instead of jarsigner. jarsigner supports only the Signing Scheme v1, while apksigner supports multiple signing scheme versions, and it determines the scheme version to use depending on the SDK version. It is also, already included on the Android SDK.
…simultaneously while managing the state of each group individually
"yarn" -> "npx" for new users is useful
…ork#14378 (quasarframework#14376) fix(QSelect): skip tab navigation for autocomplete input
…k#14243) * feat(ui/api): Add new top-level section 'fields' * feat(ui/ts): Generate types for 'fields' top-level section * feat(docs): Add support for 'fields' top-level section
…on the "describe" command quasarframework#14243
…ewIndex parameter in JSON (fix: quasarframework#12615) (quasarframework#14746) Added a description of the setIndex method parameter
In most cases we can't provide one so we add exemption. Less exemptions specified -> lower JSON footprint
…new computedProp "currentComponent" so their methods can be exposed quasarframework#14749
"mention about" does not seem grammatically correct
Add files via upload
Initialed lo mjs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
The PR fulfills these requirements:
dev
branch (orv[X]
branch)fix: #xxx[,#xxx]
, where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: