Opened 10 years ago
Closed 10 years ago
#13329 closed feature (invalid)
Adjusting jQ 2.0 $.extend to align with ES6 Object.assign
Reported by: | jdalton | Owned by: | jdalton |
---|---|---|---|
Priority: | undecided | Milestone: | None |
Component: | unfiled | Version: | git |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
I wanted to bring up the topic of adjusting $.extend to align with ES6 Object.assign (basically restricting to iterating over own properties of source objects).
Change History (3)
comment:1 Changed 10 years ago by
comment:2 Changed 10 years ago by
Owner: | set to jdalton |
---|---|
Status: | new → pending |
comment:3 Changed 10 years ago by
Resolution: | → invalid |
---|---|
Status: | pending → closed |
Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!
Note: See
TracTickets for help on using
tickets.
Well the 1.9 and 2.0 APIs need to behave the same way, so if we did it in 2.0 we'd need to add it to 1.9.1 as well. This seems like it becomes a request to make all of jQuery 1.9.1+/2.0+
hasOwnProperty
-guarded, so no barefor/in
*anywhere* in the lib, fixing$.extend()
, etc.Clearly we can't depend on ES6 features being present yet, even in 2.0. Exactly when does this issue arise for a user of
$.extend()
?