Thanks Mark! Scaling up the support is on the roadmap, we hope to catch up with Supabaseās level by the summer this year. Supabase is really great at support.
Send me your project link in direct message and I will look into it
We are having an issue with the basic weweb input component. So, currently the enter event on the input is not working
Hi,
Today I opened Weweb and read something about a ānew powerful datagridā ā did this became automatically part of my dynamic lists? Or do I need to take action - and if so, what?
Thanks.
@Raphael
Here is some evidence of what is happening:
All modals have the following structure.
- Native component
- Modal
- Overlay
Previously, the component did not have a native z-index, which made us configure it using the Modal and Overlay z-index. When the Modal and Overlay z-index was updated, it was broken. All the platformās popups and sheets were missing, āunderneathā all the other elements. Replacing the z-index for the companion makes it appear again.
The biggest problem is responsiveness. The modal uses 96% height and width on desktop and 100% for tablets and mobile. Responsiveness worked perfectly, even with the menu and headers on mobile phones, it didnāt break.
Now, if I apply 100% all responsiveness breaks. I had to go back to using 100vh and 100vw, and the elements can only be displayed with the menu and headers on mobile phones. This breaks flows, creates crashes and breaks the elements.
The sheet, for example, had this design, as in the image, using the configuration that was in yesterday.
But when I updated the configuration it was all broken.
the same applies to pop ups, which no longer stretch the percentage, and I can no longer make it āfullscreenā
Looks very promising! Great work!
Congrats on the update team! Looks solid. Whereās my datagrid tho?
Very exciting!
Is the new pricing still per workspace? There is only one mention of workspaces on the pricing page by the partner program.
itās almost in production but not yet! Should be later today.
Responsiveness broke for me too
coming by the end of the day
I just spent 370k tokens on one prompt, and the AI result was complete nonsense. You should add some kind of assessment of the token usage or some way to stop the process.
It is impossible to estimate your token usage and spending this much on a single prompt will hold me back on the usage.
This change should be reverted now. Can you confirm that itās working as it was? We apologize for the inconveniences.
Congratulations all - flagging that since the update, copy and pasting OUT of the custom JS code editor omits all indented code sections.
Also copy & pasting variables in formula no longer works. For example, copying the below:
And pasting it results in:
This should be fixed now, can you confirm?
I highlighted the datagrid and created a new test component from it. I told the AI to add a column that displays a circular progress indicator. The written response said that it created that column, which it did, but it only included numeric values and not a progress indicator. One of the new pages about the 3.0 update states that weāll be able to edit the component in the future. Am I way too early, or is this beyond the scope of what the AI can do based on the way the component is built?
Thanks.
Confirmed, fixed! Thanks!