Mathieu CAROFF
Mathieu CAROFF
I also get the same error with https://github.com/acro5piano/graphql-rest-proxy/blob/master/examples/schema.graphql
It appears I did my test wrong with `examples/schema.graphql`. It actually works, both on Windows and on Linux. However, the first GraphQL file content I brought still provokes the `Cannot...
I'd like to propose a variant of the multi-colon syntax: ```ts { x:: number } { x:: number = 123 } { xin: xout:: number } { xin: xout:: number...
Here is another idea of syntax, which resembles the "Auto spread" proposition of @dragomirtitian: `{...}: { x: number }`. It actually extends the syntax of "Interface spread to variable" proposed...
## Content - [Content](#content) - [Vocabulary](#vocabulary) - [All the issues I could find](#all-the-issues-i-could-find) - [Reason(s) to decline the feature request (back in 2016)](#reasons-to-decline-the-feature-request-back-in-2016) - [Proposition(s) with unusable syntax](#propositions-with-unusable-syntax) - [Formatting...
Here is my order of preference on these 10 alternatives, from most wanted to least wanted: - spread_with_remap - auto_spread - parentheses - colon_square - double_colon - _--approval threshold--_ -...
As I imagine it, `{...}: InterfaceType` would be an invalid syntax. auto_spread would be a rigid syntax with four braces in it: `{...}: {}`.
# `angle_bracket_after_remap` ```ts { x } { xin: xout = 123 } ```
# `angle_bracket_before` ```ts { x } { xin: xout = 123 } ```
# `as_type` ```ts { x as number } { xin: xout as number = 123 } ```