@rstoenescu in current version (0.16) is there option to limit visible options in q-select? So it should work like it work now, listing all options, but to limit number of visible without scrolling. Other, non visible, should be visible after scrolling up/down… issue is when you have bigger list, you can not limit visible part to for example 5, instead it show you 15 which take almost whole screen. Thanks in advance and thanks for awesome framework 
Just update. The issue was that we were returning double CORS headers, one from Nginx and one from Laravel application, which was fine on android, but on ios didn’t work. Once when we removed one from the Laravel application and improved Nginx config to return headers even in the case of 4xx reposes it starts to work normal…
I hope this could help someone
Just update. The issue was that we were returning double CORS headers, one from Nginx and one from Laravel application, which was fine on android, but on ios didn’t work. Once when we removed one from the Laravel application and improved Nginx config to return headers even in the case of 4xx reposes it starts to work normal…
I hope this could help someone
Hi,
I have one Quasar application that was working already for some time on web/android/ios, but after the last update of code from this week, it just stops working only on iOS. The backend part, at least one that handles CORS is not changed in this update. After some debugging and trying to get some useful information that I can act upon, I have just discovered that on each AJAX request it get “Network Error”. It only happens on iOS, Android, and Web applications work normally.
Does anyone have some idea what could be wrong and point me in the right direction to solve this? I have used Cordova for mobile applications and its configuration also didn’t change in this last update of code.
Thanks in advance.
Is this part of quasar project? In quasar project you can use Vue.extend({}) and use quasar components by just adding them in quasar.config.js framework.components array. But I have never used string template inside project, but that should not be different if I’m right…
Can you provide more information about your project and where is this file inside of that project?
@rstoenescu in current version (0.16) is there option to limit visible options in q-select? So it should work like it work now, listing all options, but to limit number of visible without scrolling. Other, non visible, should be visible after scrolling up/down… issue is when you have bigger list, you can not limit visible part to for example 5, instead it show you 15 which take almost whole screen. Thanks in advance and thanks for awesome framework
@benoitranque yes I read it and I understand that part. My code works exactly like I expected, but what I’m asking is there some “hidden” things that I don’t see at the moment about this usage.
Here is complete boot plugin code:
import api from ‘src/api’
// leave the export, even if you don’t use it
export default ({ app, store, Vue }) => {
let tokenKey = api.getTokenKey()
let token = localStorage.getItem(tokenKey)
// assign api to Vue for easier access, like this.$api
Vue.prototype.$api = api
if (!token || token === ‘undefined’) {
/* eslint-disable-next-line no-new */
new Vue(app)
}
api.checkToken(token)
.then(() => {
store.commit(‘apiAuth/changeIsGuest’, { status: false }, { root: true })
store.commit(‘apiAuth/changeToken’, { token: token, store: false }, { root: true })
})
.catch(() => {
// we wish to remove token so we don’t need to check it again on page refresh
localStorage.removeItem(tokenKey)
})
.finally(() => {
/* eslint-disable-next-line no-new */
new Vue(app)
})
}
Thanks in advance for any suggestion
I have just found this thread. I’m new to quasar and I was need ajax call to validate token found in localStorage. I failed to do it with regular plugin and I searched for solution. @Slade suggestion to add it to “boot” plugin works really good. Is there something that I’m missing or doing wrong with this approach?