@beets Thank you for the tips.

@dobbel I meant “at the top” instead of “on top”, like a sticky header in a QTable. As pointed out by @Ilia , the position: sticky; top: 0px; does indeed work (I had forgotten to add the top )

@beets Thank you! This works perfectly. I did tried adding a <div class=“fit scroll”> previously, but now I know the problem lies on “absolute-full” in the q-page-container. Much thanks!

@dobbel If my response wasn’t clear, I’d agree this is definitely a bug in the documentation at least. Although I guess it does say its original data type and not its original data types ^^

I think recursively serializing an object would be nice, and actually looks like it’s being worked on: https://github.com/pdanpdan/quasar/commit/5b25d0f9a58503553d9f0d1a659cba3116172125

@beets Excelent…
Muchas gracias…

@khoado

here’s a few threads that might help:
https://forum.quasar-framework.org/topic/5790/multiple-spa-entry-points-with-a-single-codebase/2?_=1608302449473

https://forum.quasar-framework.org/topic/6065/how-can-i-conditionally-include-exclude-pieces-of-my-app/4

https://forum.quasar-framework.org/topic/5495/multi-part-application/7?_=1608302449470

It looks like troubleshooting the Push Notification from a local Dev Server is working just fine. I see in the dev tools the notifications from firebase.

@dobbel thanks for the reply and sorry for the late response.
your solution works on paper but the tick strategy is lost, :ticked.sync is also lost - both important things to reduce code. cleanest way would be to somehow resolve the bug only by props or something

@metalsadman yeach true

Take the code from the docs on labeled “Clearable is equivalent to” and put it in your append slot.

Here is the code to make it work with your codepen

<template v-slot:append> <q-icon v-if="search" name="cancel" class="cursor-pointer" @click.stop="text = null" ></q-icon> <q-icon name="search"></q-icon> </template>

@beets Thanks! Didn’t thought it was that easy. 😉

@mosiki You should not try to require index.js from src-ssr after build, as that file must be processed by quasar cli. You could try adding firebase functions in another file in src-ssr and require that, but I’m not familiar with firebase.

Think of it this way though, anything in src-ssr is the source files for an express sever. Once you build, the express server gets built to the dist dir and is independent of quasar at that point. Usually to deploy you just copy the dist dir to the server, yarn install, and run.

@operez2000 The express server under src-ssr does not run with Electron. You would have to re-create the express api under src-electron. You could share code between the two and require the shared code in both src-ssr and src-electron. But it’s not always the best idea to run a server locally this way, depending on your security model since the endpoint is completely exposed to any process running on that user’s computer. Also, the user might be running something else on that port (which can be solved by using a randomized port on start.)

But better yet is to use electron’s ipc to communicate from the frontend to the backend. It would require some more work to make the frontend either call ipcRenderer or axios depending on the mode. You still could share code between ssr and electron, but it involves more work.

@beets
Ah, forgot the ginger and Apple. And I also add one Jalapeno pepper and fresh garlic with the mix. 🙂
Gets real spicy. That’s actually counts as one meal, and I eat a normal lunch as my second meal.

@metalsadman said in QMarkdown TOC and Vue composition api:

@gvorster should be ref(null) I think. You should prolly await a nextTick in your function too. If you translate the snippet to composition would look about like this:

... const markdown = ref(null) const toc = ref(null) ... async func... await context.root.$nextTick() toc.value = markdown.value.makeTree(toc) ...

Thanks, I tried nextTick but got the same error.

But anyway, I can see the passed TOC data inside the function so I can work with that to render it above the markdown text.

function onToc(toc) { console.log(toc); }

Selection_006.png

I don’t have a mac Only I can say that chrome in IOS has the same problem

@iamtetea if you understood the code, content is just the data array converted into string delimited by commas, you can do whatever with it just follow the correct pattern for it to be a valid csv format.

Thank’s for your help.
Since my controls are bound to an array, I just call the function passing the array key.

<div v-for="item in tipo_pax" :key="item.tipo" :bind="item" class="row""> <div style="width: 50px; font-size: 16px;">{{item.tipo}}</div> <q-btn @click="decrementa(item.tipo.toLowerCase())" class="on-right" dense round size="sm" icon="remove" color="secondary"/> <q-input hide-bottom-space class="on-right" borderless input-class="q-ma-none" v-model="lclPacote[item.tipo.toLowerCase()]" style="height: 25px; padding: 0px;" input-style="text-align: center; width: 30px;" /> <q-btn @click="incrementa(item.tipo.toLowerCase())" round size="sm" icon="add" color="secondary"/> </div>

and the function is :

incrementa (tipo) { this.lclPacote[tipo]++ }, decrementa (tipo) { if (this.lclPacote[tipo] > 0) { this.lclPacote[tipo]-- } }

and the object :

lclPacote: { adt: '0', chd: '0', inf: '0', sen: '0', est: '0', free: '0' },

It works fine

Thank you