One API feedback I have is about a bit more convenience for

@usable_as_dagster_type

. We take advantage of custom `DagsterType`'s for loading various combinations of names from pipeline config, and we "resolve" these names against a database. Ideally, we would be able to pass a type check function to the

@usable_as_dagster_type

that gets composed with the instance-of check

PythonObjectDagsterType

performs. Without that hook, we end up falling back to subclassing

PythonObjectDagsterType

, and using

make_python_type_usable_as_dagster_type

to register our type during module load.

thanks for the feedback @Cagatay K. I filed an issue to track this: https://github.com/dagster-io/dagster/issues/4154