What's the best practice for documenting config fields? I'm making a values resource for the config options common to the whole job. I don't see a way to add descriptive strings along with the typing information I can pass in there. I can leave comments in an example yaml file, but wondered if there's a better way.

The config fields have an optional description field that will show up in the typeahead if you fill them out: https://docs.dagster.io/_apidocs/config