Plugin functions are uncallable in response to events about vorlonjs HOT 15 CLOSED

I will definitely need more info to help.Can you commit your code in a temporary branch?

from vorlonjs.

@deltakosh I just pushed it to the components branch

from vorlonjs.

Here is the line that throws: https://github.com/MicrosoftDX/Vorlonjs/blob/components/Plugins/Vorlon/plugins/domExplorer/vorlon.domExplorer.ts#L220

from vorlonjs.

@deltakosh I am adding a listener to handle refresh events thrown from within the DOM Explorer's DOM tree panel. It appears that something is taking issue with a Plugin's function being invoked from inside an event handler.

Is there some form of custom, object-checking/locking CSP that the project or TypeScript employs to prevent this?

from vorlonjs.

Not to my knowledge:(

from vorlonjs.

Warning there is a misunderstanding here: the refresh function does not exist dashboard side. You have to send a refresh message to the client side of the plugin.

from vorlonjs.

Like this:
Core.Messenger.sendRealtimeMessage(this.getID(), { type: "refresh" }, RuntimeSide.Dashboard);

And then you have to update this function:
https://github.com/MicrosoftDX/Vorlonjs/blob/components/Plugins/Vorlon/plugins/domExplorer/vorlon.domExplorer.ts#L188

in order to add a "refresh" case

Does it make sense?

from vorlonjs.

@deltakosh this event is not coming from the client, it is coming from the dashboard's own UI/elements. If you log this.refresh in the scope of that event handler it clearly exists.

Why would a Plugin be charged with creating its own dashboard UI and have no access to its own public/private functions? I don't understand that aspect, can you clarify?

from vorlonjs.

@deltakosh you said this in the comment above: "Warning there is a misunderstanding here: the refresh function does not exist dashboard side", but then how come I can log the function and execute it? A security warning makes me thing the object is protected in some way. If the function didn't exist, wouldn't that handler immediately throw undefined when binding/calling it?

from vorlonjs.

Actually it exists as the same code is executed on the client and on the dashboard. But the dashboard is not executed on the device, so there is no reason to execute refresh() function dashboard side. Right?

You need to use the messenger as I shown before to send a message to the client part of the plugin in order to execute refresh on the device

from vorlonjs.

I mean: the click will happen on the dashboard, the dashboard is gonna use the messenger to send a message to the client, the client will receive the message, process it and resend the result back to the dashboard

from vorlonjs.

@deltakosh hmm, ok, I thought refresh() was the function that performed that flow (sending a message to the client and grabbing latest). I will take another look.

from vorlonjs.

Ok I understand so :)

from vorlonjs.

@deltakosh got it working, thanks for the clarification :)

from vorlonjs.

My pleasure my friend

from vorlonjs.