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

Updated Laotian translation #3

Merged
merged 3,712 commits into from
Nov 19, 2022
Merged

Updated Laotian translation #3

merged 3,712 commits into from
Nov 19, 2022

Conversation

Vongsi
Copy link
Owner

@Vongsi Vongsi commented Nov 19, 2022

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Documentation
  • Code style update
  • Refactor
  • Build-related changes
  • Other, please describe:

Does this PR introduce a breaking change?

  • Yes
  • No

The PR fulfills these requirements:

  • It's submitted to the dev branch (or v[X] branch)
  • When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
  • It's been tested on a Cordova (iOS, Android) app
  • It's been tested on an Electron app
  • Any necessary documentation has been added or updated in the docs or explained in the PR's description.

If adding a new feature, the PR's description includes:

  • A convincing reason for adding this feature (to avoid wasting your time, it's best to start a new feature discussion first and wait for approval before working on it)

Other information:

hawkeye64 and others added 30 commits August 28, 2022 09:26
…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: 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
…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
rstoenescu and others added 29 commits October 28, 2022 20:14
…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
@Vongsi Vongsi merged commit e5a4ae3 into master Nov 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.