Posts made by danielcommesse

@rstoenescu So glad to hear you are feeling better and healthy!!!

The problem is with chrome, safari and microsoft edge, opera, the only browser that it’s working is firefox.

Chrome:

Your connection is not private
Attackers might be trying to steal your information from quasar.dev (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_DATE_INVALID

Help improve security on the web for everyone by sending URLs of some pages you visit, limited system information, and some page content to Google. Privacy policy
quasar.dev normally uses encryption to protect your information. When Google Chrome tried to connect to quasar.dev this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be quasar.dev, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Google Chrome stopped the connection before any data was exchanged.

You cannot visit quasar.dev right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later.

Edge:

Your connection isn't private
Attackers might be trying to steal your information from quasar.dev (for example, passwords, messages, or credit cards).
NET::ERR_CERT_DATE_INVALID
quasar.dev uses encryption to protect your information. When Microsoft Edge tried to connect to quasar.dev this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be quasar.dev, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Microsoft Edge stopped the connection before any data was exchanged.

You can't visit quasar.dev right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later.

Safari:

Safari Can't Open the Page
Safari can't open the page "https://quasar.dev" because Safari can't establish a secure 
connection to the server "quasar.dev".

I tried to delete the security policies on Chrome, but you cannot delete preloaded entries.

Hey Razvan, hope you will get better, it’s ok to take some time off to heal, your mind and body will thank you later. You will come back stronger than ever.

The best wishes for you and your family!

Hi quasarians, I’m having trouble accessing quasar.dev site in chrome, edge and safari, however it is working great on firefox. This has been happening for a while now.

The error that it gives me is the NET::ERR_CERT_DATE_INVALID, several weeks before lot of devs where having trouble also, I think it may be related to HSTS.

Is there a way around this?

Thanks for your help!

@Hawkeye64 I actually got it to work, don’t know if it’s the best solution (probably not), but seems to work just fine:

• I cloned the prism repo.
• made a folder in my project prism
• copied ONLY the file components/prism-markup-templating.min.js (does not work without this file), and then imported it in my project before the export default.
• Then did the same for every language that I wanted to use (just like 5 in my case and 6 files copied in total).
• Example:

import('@/prismjs/components/prism-markup-templating.min.js')
import('@/prismjs/components/prism-php.min.js')
import('@/prismjs/components/prism-python.min.js')

Hope it helps someone else. Or better, maybe someone else has a better solution/implementation.
I will mark this as solved for the moment.

Hi quasarians!,

I’m using the QMarkdown component. It supports syntax highlighting, but just comes with a few languages by default. I am trying to add more languages without success.

According to the official docs, you can extend Prism (the syntax highlighting library) like this:

<q-markdown :extendPrism="extendPrism" />
methods: {
  // to extend Prism
  extendPrism (Prism) {
    // this uses the 'autoloader' plugin
    // https://prismjs.com/plugins/autoloader/
    Prism.plugins.autoloader.languages_path = 'path/to/grammars/'
  }
}

However I’m getting the error:

[Vue warn]: Error in render: "TypeError: Cannot set property 'languages_path' of undefined"

This is the Prism object in the console:

{Prism: {…}}
Prism:
Token: ƒ Token(type, content, alias, matchedStr, greedy)
disableWorkerMessageHandler: undefined
fileHighlight: ƒ (container)
filename: "http://localhost:8085/22.js"
highlight: ƒ (text, grammar, language)
highlightAll: ƒ (async, callback)
highlightAllUnder: ƒ (container, async, callback)
highlightElement: ƒ (element, async, callback)
hooks: {all: {…}, add: ƒ, run: ƒ}
languages: {markup: {…}, xml: {…}, extend: ƒ, insertBefore: ƒ, DFS: ƒ, …}
manual: undefined
matchGrammar: ƒ (text, strarr, grammar, index, startPos, oneshot, target)
plugins: {}
tokenize: ƒ (text, grammar)
util: {encode: ƒ, type: ƒ, objId: ƒ, clone: ƒ, getLanguage: ƒ, …}
__proto__: Object
__proto__: Object

I’ve noticed the plugins property is empty.

Any help?

Thanks in advance!

Thanks for your answer @rstoenescu, will give MDI svg icons a try!

Awesome, really great work as always!!!

Question, does QIcon svg support means we can use now the Material Design two tone icons?

@metalsadman Oh yes, it works!!!, damn Quasar is absolutely great!!!

Thank you very much @metalsadman.

I updated the codepen to make it more clear.

@metalsadman Initially it doesn’t, but focus any input and type a letter, as the mask is only accepting numbers, it won’t fill the mask but the model will be filled with the mask and mask tokens replaced by ‘_’.

For my frontend validation I require that input inputs are touched (vuelidate touched), so in my forms if the user submits the form, the QInputs are touched (vuelidate touched) and the models are filled, messing with my backend validation, as it expects null values or values that complies with the mask regex (I transform the mask to regex in my backend).

Hi quasarians,

I am using QInput with a mask for a phone number like this: ‘(###)-###-####’.

I’m using the fill-mask attribute, because I like the feedback it provides as filling the mask.

However the fill-mask attribute fills the model even when the you have typed nothing in the QInput.

I have regex validation on my backend and this is causing me problems.

I know probably this is the expected behavior to fill the model, but it would be cool to not fill the model and have the input guiding that the fill-mask attribute provides.

Any help is really appreciated, thanks in advance!

Here is a codepen:
https://codepen.io/danielcommesse/pen/MWYVyxw?editable=true&editors=101

@ddenev I also put 34.65.228.161 in my /etc/hosts and now I can access it.

I guess they’re doing lot’s of changes in the hosting/backend, hope everything gets fixed soon!!!.

It’s also down again for me…, also using Cloudflare 1.1.1.1.

There are also steps for other platforms, however I did not test the other platforms.

For everyone that is having trouble accessing quasar.dev if you’re on a mac follow the steps in here https://developers.cloudflare.com/1.1.1.1/setting-up-1.1.1.1/mac/

This will change your DNS to use Cloudflare DNS by default. This solved it for me. Hope it helps!.

I have flushed my dns and still can’t access from México.

In my case, honestly, it was about Laravel, I embraced Vue because I use Laravel and it comes default with it. After using it a while I fell in love with Vue, it makes so much sense to me, and it is really a joy to work with it.

After using it a while, I discovered Quasar, being able to do desktop, Android, iOS, PWA’s, and web apps from single codebase it just blew my mind. So I went all in with Quasar, now Quasar handles all the frontend as an PWA SPA and Laravel handles the backend as an API.

Also in my opinion, Quasar has the most complete set of components, the components are really well designed, and as a framework it’s very superior to the React Frameworks I have checked, it totally blows Material-UI, the most popular Material Design framework of React.

It all comes down to productivity, with Vue and Quasar, I’m much more productive than I would be with React.

Also Vue has been gaining traction, now even Apple uses it, check https://developer.apple.com/tutorials/swiftui.

Also I trust Razvan and Evan You way more than I trust Facebook.

@mas For performance I really don’t know, I don’t think it really makes a significant difference, in my case I use to catch the axios promise in the action when is an action that I use only one time or the then/catch proccess is the same wherever I use it, but I have times where I have a same action that I use in different places, and depending where I use it the then/catch proccess is different, then I handle it at the component level. For example:

I have an endpoint in my API where I retrieve notifications, but I show them on different places and devices (cordova, pwa, etc…) and I handle the then/catch different based on where the notifications are shown and which device is being shown on. For that I prefer to handle them at the component level and not crowd my actions file. Hope it helps!

@mas You may even return the $axios promise and catch it at the component level:

export function myAPI (context, data) {
  this._vm.$q.loading.show()
  return this._vm.$axios.post(`my-API-path`, data)
}

Then in your component

import { mapActions } from 'vuex'
export default {
  methods: {
    ...mapActions(['myAPI'])
    // Or if you're action is in a module
    ...mapActions('you-module', ['myAPI'])
  },
  hitMyAPI () {
    this.myAPI().then(response => {
      this.$q.loading.hide()
      this.$q.notify({
        message: 'Your message',
        color: 'positive'
      }
    }).catch(error => {
      this.$q.loading.hide()
      this.$q.notify({
        message: 'Your error',
        color: 'negative'
      }
    })
  }
}