Is there a way to retrieve what runConfigData is missing from a config schema via GraphQL Api? P.S Not the PipelineConfigValidationInvalid error message.

PipelineConfigValidationInvalid

has an

error

field that returns

PipelineConfigValidationError

which contains

path

/

stack

/

reason

you can use

I noticed that but my use case is different here. I don't want to parse the info regarding which config parameter is missing from the message string. Would like to avoid unnecessary code. Thanks for the response though!

just to clarify the things i mentioned above are typed fields in the the GraphQL schema, not parts of the

message

string

Oh yes I did try out the typed fields in dagster but they don't provide me anything regarding my use case