-
Notifications
You must be signed in to change notification settings - Fork 47
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
Missing parsed information #79
Comments
flag for optional property is implemented in this pull request I made #80 |
Things left open:
:) About the inline types... We need to think about a reasonable and good way to parse those things. It shouldn't kill the parser by loading recursive stuff to do. |
Another important feature is:
This code
results in this
|
and
|
Yep, inheritance is already present in #88 |
@ondratra a question: |
@buehler Imho it is false. When async is explicitly stated it always has to return Promise. Even TS compiler will force you to return Promise.
This function is not explicitely stating async yet it's returning Promise
This async function calls awaits on another async function.
Notice difference between Because of that I think parser should return |
I can definitely live with that explanation. |
I'm going to close this issue in favor to propper issues for each feature :) |
Parser unfortunately doesn't return full information about parsed code.
Right now I know about missing
{ myProperty?: string }
){\n email: string\n }
I can parse finish parsing by recursive call of
parser.parseSource()
, but it's very inconvenientCan we get this fixed, please?
The text was updated successfully, but these errors were encountered: