Definitely on the right path!

Read about more new features and community progress here: filamentphp.com/content/danh...

❤️ Please consider sponsoring the framework on GitHub, every contribution helps us dedicate time to building new features, fixing bugs, and supporting users:
github.com/sponsors/dan...

Join us for a special community event on Discord to:
✨ Walk through what's new in v4
🛠️ Hear from the core team
❓ Ask your questions live during our open Q&A session
🤝 Hang out with fellow devs and celebrate together!

filamentphp.com/discord

Hey! Not sure at the moment, sorry. I think probably not.

🔥🔥🔥

Hey, the query builder is meant to be used above the table: check the second code snippet on the query builder docs page

Above the table there should be plenty of space. On mobile devices it will put the inputs onto their own lines, but we don’t have container queries to do that on desktop in v3

Finally, I have built a way to build "plugins" for the rich editor and rendering system, to register any TipTap JS / PHP extensions and custom toolbar items. If you register a TipTap JS extension, it only gets loaded onto the page when you are using a rich editor, not on every request.

You can also "register" rich content fields in an Eloquent model, to configure the file attachment behaviour centrally for any rich editor instances for that attribute and any times you render HTML that attribute. It's a similar mechanism to registering Spatie Media Library collections on a model.

When using the Spatie Media Library plugin, all images in that editor are stored in their own collection on the model that is using media library. If an image is removed from the content, it also gets removed from the media library collection. The `data-id` attribute stores media UUIDs.

The `data-id` attribute is then used when the editor is loaded and when content is rendered to generate temporary URLs into the `src` attributes of the images.

This has also allowed me to build an integration in the Spatie Media Library plugin for rich editor images.

In Filament v4, we switched to TipTap, which is a much more hackable editor. The file upload system is completely redesigned, which now only saves uploads permanently when the form is submitted instead of immediately. If the image is private, its path on the disk is stored in a `data-id` attribute.