Sebastian Nemeth

Obviously it's not something that fits all scenarios... it'd primarily be a syntax that API developers could opt-in to in order to make their APIs clearer at their discretion. But...

Just checking that you're noting: The error only appears on subsequent analysis of the file. The first analysis (and compiling with `tsc`) will NOT emit the error. Did you try...

Yeah... switching between VSCode and Workspace typescript versions doesn't change anything - the error appears either way. This is really interesting... I wonder what could be causing this. Also all...

I would happy to jump in a help debug this. It would be pretty fun to determine that it was my colour theme in VSCode that triggered a bug in...

To keep note, I think the fact that error is only present when the type of `arg` in `doThing` is explicitly declared is telling. When no type is explicitly declared...

I suppose I'll close this issue in favour of #57585 and track it there.

Check out my PR for my fix, which implements support for nested mappers / parsers: https://github.com/mmkal/ts/pull/248

Is there really no comprehensive xsd/xml parser/writer for typescript out there? On Wed, 27 Nov 2019 at 12:14, Franklin Chen wrote: > Unfortunately, I noticed this severe limitation several months...

Also expressing my interest in this feature! Many of the tests where inline tests are most useful are for small chunks of code where creating a separate test file is...