Just verified, all good now!

Until I updated to the most recent quasar (1.2) this morning, this code was working fine for making my calendar selection pop up when its icon was clicked on. But now nothing happens and there is no error in the console. Anyone have a clue what might have changed?

<q-input class="dinput" v-model="startdate" borderless dense stack-label :label="$t('startdate')" @input="showApplyButton=true;">
    <template v-slot:prepend>
        <q-icon name="event" color="grey-6" class="cursor-pointer">
          <q-popup-proxy>
            <q-date minimal v-model="startdate" mask="YYYY/MM/DD" :options="drangeOptions"/>
          </q-popup-proxy>
        </q-icon>
      </template>
    </q-input>

attaching an input event to the q-popup-proxy fires, so I know at least that the proxy is receiving input, but my q-date will not show.

I finally gave up trying to make this work in a subfolder. I made a new subdomain and served it as the top level. Now the location redirects work as expected.

Hi, I have enabled history mode, and it works perfectly in my dev environment, but when I try to upload my build to the server, I get nothing but 404 errors. I am pretty sure the problem is that my app does not live at the top level of this server, but in a subdirectory. (So instead of my site being at https://my.site.net/ it is at https://my.site.net/subfolder/). I have tried adding following to the nginx config, and they all fail in exactly the same way (a bunch of 404 errors):

location  /subfolder {
   try_files $uri $uri/ /subfolder/index.html;
}

location  ^~ /subfolder {
   try_files $uri $uri/ /index.html;
}

location  ^~ /subfolder {
   try_files $uri $uri/ /subfolder/index.html;
}

Does anyone know how to properly configure this for an app that lives in a subfolder? Thanks!

Does ANYONE know if this is production ready?

The github repo says “[WORK IN PROGRESS]”…is this production ready? Is there documentation somewhere? Thanks!

sure, here is my boot file:

// for when you don't specify quasar.conf.js > framework: 'all'
import { Quasar } from 'quasar'
import { i18n } from 'boot/i18n.js'

export default async ({ store }) => {
  let previouslyRestored = false
  await store.restored
  if (!previouslyRestored) {
    previouslyRestored = true
  }

  let langIso = 'en-gb'
  if (previouslyRestored) {
    console.log(store.state.rstruth.lang_prefs)
    if (store.state.rstruth.lang_prefs !== 'en-gb') {
      langIso = store.state.rstruth.lang_prefs
    }
    i18n.locale = langIso
    try {
      await import(`quasar/lang/${langIso}`)
        .then(lang => {
          Quasar.lang.set(lang.default)
        })
    } catch (err) {
      // Requested Quasar Language Pack does not exist,
      // let's not break the app, so catching error
    }
  }
}

Some important things to note:

• This relies on a vuex store and a way to persist my vuex values (I use vuex-persist but there are other ways)
• I am using a call in vuex-persist (previouslyRestored) to check if my state has been restored before I try to access values from the store.

FYI, it totally works with the code shown above. Now we have a way to set lang (for both Quasar and i18n) across restarts/reloads. This assumes that the i18n boot file is configured to export it like so (from @s-molinari medium article):

import VueI18n from 'vue-i18n'
import messages from 'src/i18n'

let i18n

export default async ({ app, Vue }) => {
  Vue.use(VueI18n)

  // Set i18n instance on app
  app.i18n = new VueI18n({
    locale: 'en-gb',
    fallbackLocale: 'en-gb',
    // enableInSFC: true,
    messages
  })
  i18n = app.i18n
}

export { i18n }

@s-molinari Since we are still on the same subject, I am now trying to also set the language for i18n at the same time, but it does not seem there is a param to pass through in the same way is there? So I assume I need to do something like this?

import i18n from 'boot/i18n.js'

export default async ({ store }) => {
    i18n.locale = myStoredLocale
}

or do you recommend another way to set the i18n locale at boot?