Allow nesting subcomponents like Images inside of Tables, Details, etc.

[jimkring]

This PR allows FastUI components to be used as the values of DataModel's passed into Table and Details components. This means that one can have a column in a table that is an Image, Button, etc.

For example, let's say I have an object with a name and an image.

from pydantic import BaseCase
import fastui.components as c

class MyType(BaseClass):
  name: str
  # let's make icon a fastui `Image` component type
  icon: c.Image

# create an instance
my_object = MyType(name="meowzer", icon=c.Image(src="image.png"))

# try to render it inside of a `Details` component.
c.Page(
  components=[
    c.Details(data=my_object)
  ]
)

Before this PR:

name	meowzer
icon	src: image.png, type: Image,

After this PR:

name	meowzer
icon

FYI: @samuelcolvin @sydney-runkle

Note: Implements enhancement request #293

fix #293
fix #267

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

[jimkring]

@hramezani since you've been doing some work in Table and Details, I'd be curious to hear your thought/feedback on this PR, too.

[hramezani]

@hramezani since you've been doing some work in Table and Details, I'd be curious to hear your thought/feedback on this PR, too.

Thanks @jimkring for the PR.
The change looks easy and good to me 👍 . let's wait for @samuelcolvin or @sydney-runkle to review.

[samuelcolvin]

Beyond the philosophy side of things, I'm good with this.

[samuelcolvin]

I think there are two clean options here in terms of ways forward:

1. Something like add FormattedText component #29 where we define a subset of components (or maybe they're not even included in regular components) that can be used in buttons and table cells and paragraphs (although I'm already seeing a problem that stuff like images belong in table cells but I think are illegal in paragraphs or buttons)
2. We allow anything in a table cell, and DisplayObject just becomes a component, which I've wanted otherwise anyway. Perhaps we have some logic for the default components for table cells is a DisplayObject

Or maybe route 3 is we merge this to help @jimkring and worry about the ultimately correct solution later?

[sydney-runkle]

@jimkring,

Awesome work here. Let's go with route 3 as mentioned by @samuelcolvin - merge this now, and refine nestable subcomponents down the line!

[jimkring]

Fantastic! Looking forward to 0.7.0!

Thanks everyone for reviewing and collaborating on this.