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

Should we allow more than just strings as module attributes? #59

Open
littledan opened this issue May 20, 2020 · 1 comment
Open

Should we allow more than just strings as module attributes? #59

littledan opened this issue May 20, 2020 · 1 comment

Comments

@littledan
Copy link
Member

We've talked about generalizing to static-looking object literals in general. A more scoped generalization, proposed by @Jack-Works , would be just allowing Numbers, BigInts, null, booleans, and (maybe?) undefined.

I want to propose that we could go to Stage 2 with just strings, and consider generalizations between Stage 2 and 3. In particular, I believe the generalizations @Jack-Works proposes would not be core to the data model or other fundamental decisions that we need to assess for the viability of the proposal overall.

@xtuc
Copy link
Member

xtuc commented May 22, 2020

I agree with it being a stage 3 concern. One thing I would like to avoid is promoting hacks to pass other types by parsing the strings like "null", "false", ... in the proposal or make people thing that's something we planned.

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