Enzo Innocenzi
@innocenzi.dev
Developer experience enthusiast. Code is art. I love Tempest, Laravel, Vue, Vite, Tailwind, Rust and Bevy.
» tempestphp.com • hybridly.dev • innocenzi.dev
» tempestphp.com • hybridly.dev • innocenzi.dev
I wish it accepted `null` as an input too
September 8, 2025 at 5:42 PM
I wish it accepted `null` as an input too
The ORM is not designed for it and thus doesn't provide a driver for it
However it would probably be super easy to register the PHP driver for MongoDB, and to use Tempest's mapper to map query results to models
However it would probably be super easy to register the PHP driver for MongoDB, and to use Tempest's mapper to map query results to models
June 28, 2025 at 1:47 AM
The ORM is not designed for it and thus doesn't provide a driver for it
However it would probably be super easy to register the PHP driver for MongoDB, and to use Tempest's mapper to map query results to models
However it would probably be super easy to register the PHP driver for MongoDB, and to use Tempest's mapper to map query results to models
Hey, I just tried you and you seem really nice, very customizable and you have a command palette, it's awesome
Design wise though, you'd need a fresh coat of paint. Buttons especially look pretty old and built-in themes don't help 😵💫
Design wise though, you'd need a fresh coat of paint. Buttons especially look pretty old and built-in themes don't help 😵💫
June 25, 2025 at 9:21 PM
Hey, I just tried you and you seem really nice, very customizable and you have a command palette, it's awesome
Design wise though, you'd need a fresh coat of paint. Buttons especially look pretty old and built-in themes don't help 😵💫
Design wise though, you'd need a fresh coat of paint. Buttons especially look pretty old and built-in themes don't help 😵💫
What did you get instead? A Polestar?
April 15, 2025 at 6:40 PM
What did you get instead? A Polestar?
That extension looks NICE.
April 2, 2025 at 3:54 PM
That extension looks NICE.
On the front-end the story is quite different than on the back-end, because thanks to TypeScript you can have autocompletion for both route names and arguments.
If the URI changes on the back-end, it would be updated automatically as well—and if the name changes, TypeScript can warn you about it
If the URI changes on the back-end, it would be updated automatically as well—and if the name changes, TypeScript can warn you about it
March 30, 2025 at 6:29 PM
On the front-end the story is quite different than on the back-end, because thanks to TypeScript you can have autocompletion for both route names and arguments.
If the URI changes on the back-end, it would be updated automatically as well—and if the name changes, TypeScript can warn you about it
If the URI changes on the back-end, it would be updated automatically as well—and if the name changes, TypeScript can warn you about it
Yes, definitely—this is not an attribute problem specifically, but a design choice to not use named routes in Tempest
March 30, 2025 at 11:59 AM
Yes, definitely—this is not an attribute problem specifically, but a design choice to not use named routes in Tempest
In Tempest, routes don't have names, so generating routes from a client is an unsolved space :/
March 30, 2025 at 10:27 AM
In Tempest, routes don't have names, so generating routes from a client is an unsolved space :/