# Is it too late to fix \`Object.entries\` ???

**URL:** <https://es.discourse.group/t/is-it-too-late-to-fix-object-entries/1407>\
**Category:** 💡 Ideas\
**Tags:** proposal\
**Created:** [July 25, 2022, 12:59pm UTC](https://es.discourse.group/t/is-it-too-late-to-fix-object-entries/1407 "2022-07-25T12:59:00Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![WebReflection](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/webreflection/32/248_2.png) [@WebReflection](https://es.discourse.group/u/WebReflection)\
**Post date:** [July 25, 2022, 6:11pm UTC](https://es.discourse.group/t/is-it-too-late-to-fix-object-entries/1407/12 "2022-07-25T18:11:00Z")

</div>

> [@bakkot](#):
>
> `Object.fromEntries` will also allow you to pass in _numeric_ keys, which it will cast to strings

both methods are meant to represent objects ... having keys as numbers rather than strings, or even boolean, or any other primitive coercing to string just fine, is not an issue here, the issue is about loosing `symbols` instead in the process, which is also another primitive ... why all others can be perpetuated as key, even as string, while _symbol_, a primitive, cannot?

> [@bakkot](#):
>
> it is too late to change either Object.entries or Object.fromEntries. If you regard this behavior as a problem, then yes, it's a problem you'll need to live with.

Nobody wants to change `Object.fromEntries`, but I am very curious to see data about the claim it's too late to change `Object.entries`, as we're not in ES5 to ES2015 era anymore, we're way beyond, and I believe nothing out there is using `Object.entries(...args)` ... please prove me wrong?

Thank you!

---

_[View the full topic](https://es.discourse.group/t/is-it-too-late-to-fix-object-entries/1407)._