ease.js - Tasks: task #12085, clone() method
You are not allowed to post comments on this tracker with your current authentication level.
task #12085: clone() method
Submitter: | Mike Gerwitz <mikegerwitz> | ||
Submitted: | Sat 09 Jun 2012 07:11:55 PM UTC | ||
Should Start On: | Wed 01 Aug 2012 04:00:00 AM UTC | Should be Finished on: | Sat 01 Sep 2012 04:00:00 AM UTC |
Category: | Core | Priority: | 7 - High |
Item Group: | Development | Status: | None |
Privacy: | Public | Assigned to: | mikegerwitz |
Percent Complete: | 0% | Open/Closed: | Open |
Planned Release: | None | ||
Keywords: | clone |
Sat 09 Jun 2012 07:38:14 PM UTC, comment #1: [Additional Information] |
Mike Gerwitz <mikegerwitz> |
Sat 09 Jun 2012 07:11:55 PM UTC, original submission:
Cloning is conventionally done in JS by copying each property to a new object. There are a couple issues with that approach for cloning class instances in ease.js:
|
Mike Gerwitz <mikegerwitz> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2015-05-20 | mikegerwitz | Planned Release | 0.2.0 | None |
Powered by Savane 3.13-4448.
Corresponding source code
Another consideration is whether or not to support deep cloning in addition to the faster shallow clone, and whether or not to deep clone by default (which is certainly the safer option, albeit less performant).
Implementing a deep clone would not be overly difficult, as the ease.js util module already has a deep clone method.