Posts made by Hawkeye64

https://github.com/quasarframework/app-extension-qmarkdown/releases/tag/v1.0.0-beta.21

• fix: issues with line numbers #33
• feat: allow alternate char to be used in place of line numbers #34
• fix: containers have too much space at bottom #32

achievement unlocked! yay!

Perfect! Love it.

https://github.com/quasarframework/eslint-plugin-quasar/releases/tag/v1.0.0-alpha.11

• feat: new rule ‘check-valid-props’
  Now supports Quasar v1+

@matroskin You mean more like a Quasar plugin, type functionality?

https://github.com/quasarframework/app-extension-qmarkdown/releases/tag/v1.0.0-beta.20

• fix: code blocks have padding on first line #28
• fix: code block using prism have extra line at bottom #29
• fix: numbers on code blocks should not be selectable #30
• fix: change background-color to background #31

https://github.com/quasarframework/app-extension-qmediaplayer/releases/tag/v1.0.13

• fix: media with no duration shows “Infinity: Nan” #73

https://github.com/quasarframework/eslint-plugin-quasar/releases/tag/v1.0.0-alpha.7

• maintenance release
• improvements for legacy directives
• getting ready for v1 integration

https://github.com/quasarframework/eslint-plugin-quasar

https://github.com/quasarframework/app-extension-qflashcard/releases/tag/v1.0.0-beta.7

• fix: ‘quasar describe QFlashcard’ command line not working #7

You can use sqlite for mobile PWA apps? I think @Allan-EN-GB prefers to use PouchDB.

The problem is, in the boot array, it can be named anything. For instance, axious.js or http.js or ajax.js and this would be an easy one.

@livCSI Good to hear! Congrats on getting it to work.

https://github.com/quasarframework/app-extension-icon-genie/releases/tag/v1.0.2

• maintenance release
• removed Proton support

Personally, I don’t think so. Everything should be backwards compatible. And, there will be consideration for writing or rewriting components with hooks, etc.
I also don’t feel qualified to answer as no one knows what exactly the future holds…

https://github.com/quasarframework/app-extension-qwindow/releases/tag/v1.0.0-alpha.10

• fix: Property content-style does not work #10

@livCSI Thanks, I would appreciate it - make sure you tag me so I see it, if you do

also, background-image: url(~assets/background.svg); won’t work either because it’s causing the resource to be “fetched” out of the bound package. If you use css url then be sure to put your file being used into statics or use a css var and dynamically change the var after you import or request the resource.

Perhaps there is a misunderstanding of how assets vs statics works here. Your assets folder is in the direct care of webpack. It will version and bundle anything in there that is not tree-shaken. Meaning, background.svg is no longer directly there. It’s in one of your compiled js files (bound). Whereas, the statics folder is not managed by webpack, but copied to the proper location in whole at compile time.

This means you will get a 404 because the file is no longer there (as it was). When you import/require it in your code, those webpack function resolve it.

https://quasar.dev/quasar-cli/cli-documentation/handling-assets

very nice, @s-molinari !