Does dagster support UUID types in Config objects and input and outputs

In the context of Dagster's configuration system, the documentation does not explicitly mention support for UUID types within

Config

objects. Dagster's configuration system is built on top of Pydantic, and while Pydantic itself supports UUIDs, the documentation provided does not confirm that Dagster's

Config

objects directly support UUID types. For inputs and outputs of assets or ops, Dagster allows you to define custom types that can include UUIDs. However, these custom types would need to handle serialization and parsing of UUIDs manually, as Dagster's type system is designed to work with JSON-serializable types and UUIDs are not natively JSON-serializable. If you need to use UUIDs within your Dagster assets or ops, you may consider defining a custom Dagster type that serializes the UUID to a string for configuration purposes and then deserializes it back to a UUID object within the asset or op logic. This approach would involve implementing the necessary type checks and conversions manually. For more specific guidance on how to implement custom types or to check if there have been updates to Dagster's type system that include UUID support, you should refer to the latest Dagster documentation or reach out to the Dagster community for assistance.