Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: parse inline object types #95

Open
buehler opened this issue Aug 31, 2018 · 1 comment
Open

feat: parse inline object types #95

buehler opened this issue Aug 31, 2018 · 1 comment

Comments

@buehler
Copy link
Owner

buehler commented Aug 31, 2018

Related to #79

while parsing property of type Object (e.g. { myProperty: { innerPropery: string } }, the type is not fully parsed and returns values like
{\n email: string\n }

@edalex-ian
Copy link

Ah yes I've just been battling this. At least the value is still present.

As a result I can simply check for an inline object with type.match(/{.+}/s) and then recursively walk in and use parseSource. (But gee it's a pain that parseSource is async - makes the simple bit of code much more verbose than it should be.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants