Looks fine in light mode, text unreadable in dark mode.

It happened to me I deleted a column that had a foreign key constraint and for someone not working with databases, I didn't know it is a nono. It resulted in having multiple foreign keys after I added a new one to replace it.

Maybe we could either prevent it or warn the user that the foreign key should be first removed on the dropped column? Or remove the constraint with the column? Also, why c

With #4556 we now have localized eventing on subdirectories ("containedValueChanged"). We should consider using these events in our examples where we currently do path inspection on the "valueChanged" event.

Based on a quick search, looks like the following might benefit:

• examples\data-objects\primitives\src\main.tsx
• examples\data-objects\todo\src\TextList\TextListView.tsx
• [

Is your feature request related to a problem? Please describe

We can place components inline by wrapping them with ui.inline component. But currently only start and end is supported as justify values. This blocks the user from placing the components as they please.

Describe the solution you'd like

Introduce more justify values (i.e between, around, center) to `ui.in