Maybe prettify some malloy_types? #2344
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We can define a type
Prettify<T>which computes/flattens a type.
This turns a compiler error like
Object literal may only specify known properties, and 'foo' does not exist in type 'RecordExtTypeDef<FunctionParameterTypeExtensions>'.ts(2353)intoObject literal may only specify known properties, and 'foo' does not exist in type '{ type: "record"; fields: ExtFieldDef<FunctionParameterTypeExtensions>[]; }'.ts(2353), which is maybe more helpful.We could theoretically even do
DeepPrettify<T>, but this gives us less control over what things get computed...