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

map constructor does not accept arguments #3480

Closed
despairblue opened this issue Oct 17, 2015 · 3 comments
Closed

map constructor does not accept arguments #3480

despairblue opened this issue Oct 17, 2015 · 3 comments
Assignees
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@despairblue
Copy link
Contributor

Doing this: new Map([[1, 1]]) leads to the error Map constructor does not accept arguments being thrown while running in jscore. It works fine in chrome, though its using v8's native Map.

Shouldn't babel insert the core-js polyfill, which should make jscore standard compliant?

@vjeux
Copy link
Contributor

vjeux commented Oct 18, 2015

I'm in pto for two weeks, won't look into it sorry :(

@despairblue
Copy link
Contributor Author

No problem, I think I found out why that is. Probably because of #2000.
So for now I just have to stick the data types JSC supports natively.

@mkonicek
Copy link
Contributor

Hi there! This issue is being closed because it has been inactive for a while.

But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/map-constructor-does-not-accept-arguments

ProductPains helps the community prioritize the most important issues thanks to its voting feature.
It is easy to use - just login with GitHub.

Also, if this issue is a bug, please consider sending a PR with a fix.
We're a small team and rely on the community for bug fixes of issues that don't affect fb apps.

@facebook facebook locked as resolved and limited conversation to collaborators Jul 21, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 21, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

4 participants