Bug Tracker

Changes between Initial Version and Version 1 of Ticket #9937, comment 4


Ignore:
Timestamp:
Jul 31, 2011, 7:45:13 PM (10 years ago)
Author:
Robert Katić
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9937, comment 4

    initial v1  
    1 Deferred objects are state-less, jsXHR ones are not -- so, as you pointed, former objects can be duplicated (deep extend) with no issues.
     1Deferred have no states exposed, jsXHR have -- so, as you pointed, former objects can be duplicated (deep extend) with no issues.
    22
    3 However, even if deferreds will remain state-less forever, $.isPlainObject itself is part of the public API, and using it against those objects will give unexpected results.
     3However, even in case Deferred will never expose states in future, $.isPlainObject itself is part of the public API, and using it against those objects will give unexpected results.
    44
    55> the behaviour is exactly as expected and changing it here will break stuff
     
    1010> I dunno. Would the need be widespread enough to warrant some kind of "atomic object" registry that $.extend would look into to control if an object can be deep extended? I'm really no sure myself.
    1111
    12 Screw the "atomic object" crap - at least, not state-less "instances", should not be plain objects :)
     12Screw the "atomic object" crap - at least, "instances" with exposed states should not be plain objects :)
    1313
    1414