Skip to content

Enum values are not parsed correctly #103

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
Open
SrTobi opened this issue Jun 16, 2019 · 0 comments · May be fixed by #104
Open

Enum values are not parsed correctly #103

SrTobi opened this issue Jun 16, 2019 · 0 comments · May be fixed by #104

Comments

@SrTobi
Copy link

SrTobi commented Jun 16, 2019

Enum members can have optional values. At the moment they are parsed by parsing a number or a string.
The specification, however, allows full expressions, like

enum Test {
  Member = (1 <<  2)
}
@SrTobi SrTobi linked a pull request Jun 16, 2019 that will close this issue
Open
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.

correctly parse enum values SrTobi-Forks/scala-js-ts-importer
1 participant
@SrTobi