eventer | allows adding event handlers to a class

I did more research and found out that document.body.innerHTML doesn't work with Angular. Instead I used document.getElementById("plugincontainer").innerHTML in the js file and added a div into the Angular page

Check if you have

You could store the handlers in your extension class and do something like this ? Please note this code is not thread safe and need to be synchronized around dictionary and list access !

From OP's comment:

which is why I'm trying to apply a transformation then select by it. I can transform the date to the correct value required by JQ

Right after calling select, we can pipe the .ts value to remove the nanoseconds which JQ can't parse like so:

This is the issue reported in this Jira: https://jira.hyperledger.org/browse/FABN-1657

It should be fixed in current npm packages tagged unstable-2.2, and in a forthcoming v2.2.9 release of the Node SDK.

Try this event.preventDefault();

More information: https://developer.mozilla.org/en-US/docs/Web/API/Event/preventDefault

You need to log using a log message template. The message template can contain placeholders for which arguments are provided. Use names for the placeholders. In your case that means you need to add a named template position

log.LogInformation("MonitoringEvent {Event}", me);

This will create a custom property "Event" in the trace of application insights.

In your current code you do not provide a placeholder so the argument cannot be put somewhere and is ignored.

Also, do mind that application insights will probably use .ToString() on any object arguments so your best bet will be to just use mySbMsg as the argument.

More easier way is to show and hide the loader in the action itself. Before the promise, setLoader as true. And in then and catch you can hide loader.

You're getting this error because as your code currently stands, Rust does not know whether the call to self.state.on_event is valid for any type T that is indicated in the function signature fn event(&mut self, event: &T) -> std::result::Result<(), EventError>. For all Rust knows, that type T could be anything, whereas RtspState::on_event only has implementations where that type T is either PlayResponse or DescribeResponse. In fact, the compiler is telling you this with the error message the trait bound `RtspState: OnEvent` is not satisfied. You can indicate to Rust that the function event should only be valid where RtspState::on_event has a valid implementation for T by adding where RtspState: OnEvent after your return type and before your opening brace: