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.

Sign up for GitHub

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

Jump to bottom

Any plans to implement ECMA 2020 Optional Chaining? #863

Closed
twehner opened this issue Apr 8, 2021 · 3 comments · Fixed by #881
Closed

Any plans to implement ECMA 2020 Optional Chaining? #863

twehner opened this issue Apr 8, 2021 · 3 comments · Fixed by #881

Comments

@twehner
Copy link

twehner commented Apr 8, 2021

Have very compelling need to support optional chaining/existential dereferencing (myObject.someValue?.childValue and myObject.someMethod?.()). If this isn't on the roadmap yet, I'm definitely willing to devote my (or even some of my development team's) time to building it out, but this is a hefty codebase that I don't have experience with and any rough guidance on approach would be super helpful.
@lahma
Copy link
Collaborator

lahma commented Apr 8, 2021

The implementation on Jint side won't probably be that complicated, but we need parsing support in Esprima.NET which waits for jquery/esprima#2048 .

@twehner
Copy link
Author

twehner commented Apr 8, 2021

Ah, thanks. Will keep an eye on that.

@lahma lahma mentioned this issue May 4, 2021
Merged
@twehner
Copy link
Author

twehner commented May 11, 2021

Great news, thanks!

@twehner twehner closed this as completed May 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add support for Optional Chaining lahma/jint
2 participants
@lahma @twehner