Jan Potoms

I'm still on a longer standing effort to bring POST request bodies to the fetch datasource and some updates on how we handle binding values as we discussed in a...

Started sketching some changes to the release pages to deal with some of these issues https://github.com/mui/mui-toolpad/pull/583.

This isn't the right way. It's logging multiple render. It's also making logs harder to trace back to a location. Next up will be trying out running the app within...

Now that we support javascript bindings, this will require parsing and analysing javascript which makes this feature now a lot more involved than anticipated when creating this issue. I've worked...

> Is there a scenario when the bindings' resilience breaks? no that's working well.

Yep, this illustrates well what we discussed in our last retro. Components imported from urls will have to depend on `react`. In this case esm.sh rewrites the import to one...

🤔 It could become a bit tricky to deal with these `dayjs` values through the toolpad interface. Perhaps it would make sense to create a wrapper prop that converts from...

@oliviertassinari Something like this seems to work for me: ```tsx import * as React from "react"; import { createComponent } from "@mui/toolpad-core"; import { Dayjs } from "dayjs"; import TextField...

I've reduced the scope to the minimum requirement to keep us moving forward. None of this is user facing. We can introduce migration scripts and UI as the need arises,...

Intuitively I'd place this at the left. In the same area is the project hierarchy. At least, that's where almost any other tool that I can think of places it.