When commands function pointer changes, internal `commands` property is not changed
See original GitHub issueThank you for creating this component and open-sourcing it.
While using it I encountered an issue. Because of the implementation of CDU
where JSON.stringify
is used, this.validateCommands()
is not called if the implementation of some function is changed.
https://github.com/js-rcon/react-console-emulator/blob/master/src/components/Terminal.jsx#L230
I think a better compare function (based on comparing pointers) could resolve the issue. I need this because I dynamically change the behaviour of commands based on Redux state.
I might try to create a PR, I’m just very busy right now, so I keep it here if someone wants to take an initiative.
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
My object is not updated even if I use the pointer to a type to ...
Whenever a method wants to modify the receiver, it must be a pointer to the value; the method must have a pointer receiver....
Read more >Debugging with gdb - Altering Execution - Apple Developer
Open-source document that explains how to use GDB to debug programs.
Read more >Understanding Pointers in Go | DigitalOcean
You can pass the pointer to the function instead of the data, and the function can then alter the original variable in place....
Read more >User's Manual: Functions and Variables - Apache JMeter
JMeter thread variables will have not been fully set up when the functions are processed, so variable names passed as parameters will not...
Read more >Changes from v1.1 | AutoHotkey v2
If the command's first parameter is an output variable and the second parameter is not, it becomes the return value and is removed...
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 FreeTop 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
Top GitHub Comments
This is fixed as of abead75.
Turns out this wasn’t fixed after all 😆 oops. It’s actually been fixed now in cee9b4865d53b5d95338dddfe77e55019e7a1ab6 and the v3.0.3 release.