@Oliver-Buchmann - No. The forum will be open for searching/ the knowledge available until at least the end of the year. We’ll see if we keep it open longer. There is no facility to upload discussions to Github either.
@CWoodman - Ah…but you could simply wrap up QInput in your own component and in doing so, you’d have this code just once in that one component. That’s the beauty of a component system.
The article is a bit old, but the concepts still stand. Well, Vue 3 adds some new stuff to the game of composition, but that is also taught in a ton of other articles and videos.
And what’s wrong with my codepen above?
But that isn’t a validation. That a conditional change of the value.
Look at the applyDrag here: https://github.com/kutlugsahin/vue-smooth-dnd/blob/master/demo/src/utils/helpers.js
We have opened up Discussions on Github and will slowly but surely be moving the community from here to there (the people, not the posts).
The forum will be open for new topics for about a week, but we’ll be reminding everyone to start asking questions on Github.
After the week, we’ll be closing the forum for new topics. But, we are keeping it open until the end of the year as a resource. At the end of the year, we will more than likely turn the forum off.
We hope to have a better flow of work with your issues and suggestions via Github, as they can be better related to issues for bug fixing and enhancements.
“Data at rest” usually means persisted data, like in a database. You wouldn’t be encrypting data stored within files on a server.
I’m not sure what you mean by “backend files being bundled with Cordova”. I’m a noob on Cordova, but I don’t think backend code should ever be a part of a Cordova app. And certainly you wouldn’t bundle up a .env file with a Cordova app. Access to any web API on a client app should be done through the API.
For those who’d like a great video tutorial on how to upgrade Quasar (and learn about Vue 3 while your at it), check out the new Quasar v1 to v2 upgrade video tutorials from Luke Deibold
@susansiow - From the client app’s perspective, there is no difference to using normal JWTs. The difference is how the data in the JWT is encrypted and that happens all on the server side. That point should read…
Do use the JWE form of JWTs, instead of the JWS form.
Hihi… learned something new with this. Vue adds the component instance to an array element in a v-for with refs. So, you have to access the first element of the array to get the underlying component internals. Yet, if you set a ref outside a v-for loop, the instance is directly on the named element of the
$refs array. Hmm…
Getting back to your challenge…
name isn’t a QBtn property. If you add it additionally, it’s an attribute. Check my codepen now, if that is what you are looking for.
If not, I’d tend to believe you are trying to accomplish something that is not standard practice with Vue. If you’d explain your use case better, we might be able to help you find the right path to a better solution.