Redundant reactions?
See original GitHub issueI’m confused about the behavior of the following code:
const list = observable(['Hello'])
observe(() => console.log(list))
list.push('World!')
This logs ['Hello', 'World!']
twice. I expect it to log once. I get expected behavior from:
const list = observable(['Hello'])
observe(() => console.log(list.concat()))
list.push('World!')
Is this the correct behavior?
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
What is redundant reaction in structural analysis 2? - Quora
If the no. of unknowns, either reactions or member forces are more than the equations of equilibrium, then the extra unknowns are called...
Read more >8.2 Force Method using an External Reaction Redundant Force
A moment reaction component at a fixed end point A is selected as the redundant force. The external forces on the primary system...
Read more >1.10: Force Method of Analysis of Indeterminate Structures
In this method, the unknowns are the redundant forces. A redundant force can be an external support reaction force or an internal member...
Read more >Redundant Reactions of Indeterminate Beams by Principle of ...
PDF | A new methodology for determining redundant reactions of beams is presented in this paper. This methodology is based on the principle ......
Read more >Redundant Reactions of Indeterminate Beams by ... - AIAA ARC
Equation of deflection curve of this reference beam is used to solve redundant reactions of indeterminate beams. This methodology has an advantage of ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Interesting! I’m using node. Wonder why it would be platform specific. Different Proxy implementations?
I fixed the first (infinite loop issue) in the 4.1.1 release. Thanks for catching the bug 🙂
The second issue is specific to the NodeJS
console.log
implementation. Normalfor in loops
and object enumeration works, but apparently NodeJS console.log is implemented in native code. It is not gettingperson.name
under the hood (you can see this with the now working debugger).I will see if this can or should be fixed. Is this a big issue for you? I imagine this would only be used for debugging purposes.
Edit: instead of getting each property key, Node gets a shady
inspect
prop for console.log. I guess Object.prototype has a custominspect
prop in Node which points to some native magic.