Mark Bakhit

Did you ever replicate the issue with [embedded component type hints](https://github.com/idom-team/idom/issues/794#issuecomment-1283603694)?

`Object of type ComponentType is not callable` is a common type hint issue I get when trying to generically define a component. For example ```python @dataclass class Example(): my_component: ComponentType...

There is a type hint mismatch causing some annoyance on my side The `@component` decorator returns `(...) -> Component` while `ComponentConstructor` returns `(...) -> ComponentType`, making them incompatible in the...

In order for PyRight to handle this, `Component` would need to inherit from `ComponentType`.

I think the generic tuple on `use_state` might be more frustrating to use than the original implementation.

Yeah... Far too many annoying to fix type hint errors with the new `use_state`.

Seems like the main MyPy issue is `_Type` is not correctly inferred for `state` and `set_state`. Basically every usage of `state`/`set_state` result errors similar to ```Argument 1 has incompatible type...

Clearing cache fixed the issues. How strange... Maybe we can see if [sqlite_cache](https://mypy.readthedocs.io/en/stable/config_file.html#confval-sqlite_cache) resolves this issue?

Just had a thought. We could possibly leave file serialization to HTTP, and handle things on the backend. For example, adding a HTTP endpoint ```python # Uploads are given a...

If we do go down this road of serializing via websockets, it's going to be extremely important to stream the file to disk rather than buffer it in memory. Otherwise,...