changes not being observed, about object-observer HOT 3 CLOSED

Hi, thanks for a thanks and... really sorry for the delay.
Regardless of either you solved that or moved on, i'll take a look on this and see what's going on - today.
Will update here ASAP.

from object-observer.

Okay, I see what's going on.

Observation

The issue indeed with understanding of how the library works.
selectedAsset is a native JS object.
You then creating filemanagerObserver from it - i'd actually stick to the name filemanagerObservable, which is closer to the design and really descripts things:

• in itself it is not observer, but it is able to be observed - and thus you are indeed doing an .observe call on it
• we are deprated from the original selectedAsset, which is not observable but remained a simple pure object

Now, if you'd like to track a changes, you need to:

• make the changes on the filemanagerObservable and not on the original object (selectedAsset)
• you should NOT reassign the variable as a whole, like you do to the selectedAsset, since from that point you are loosing the reference to your object and getting a completely other one instead

Suggestion

Assuming, that I grasp correctly your intention here i suggest you to do the following:

• export the observable object returned from Observable.from API instead of selectedAsset
• perform the changes on the observable's properties and any-deeper but NOT on the reference self
  • NOT GOOD: observableSelectedAsset = { }
  • GOOD: observableSelectedAsset.filename = 'something'
  • GOOD: for a 'bulk' assign like the one that you show in your handleSelection method you can use Object.assign(observableSelectedAssets, { whatever })

Please, notify me if the said above makes sense and / or there is still something to clarify / help you with.

from object-observer.

Closing due to non-activity, please review my answer before reopening and if not sufficient - welcome to reopen again!!!

from object-observer.