Ivan Josipovic
Ivan Josipovic
I'm also facing this issue.
It appears that the yaml settings are pointing to the latest commit, https://github.com/danipen/TextMateSharp/blob/69616c19b39f458658c81570ab8cae6d61777e84/src/TextMateSharp.Grammars/Resources/Grammars/yaml/syntaxes/yaml.tmLanguage.json#L7 https://github.com/textmate/yaml.tmbundle/commit/e54ceae3b719506dba7e481a77cea4a8b576ae46
I tested it in netbeans which uses tm4e and it renders the yaml correctly. I will keep digging. 
Hey folks, apologies for the delay in looking into this. This issue is related to the Application Insights snippet. I could reproduce this issue by running the tests until they...
> Just installed this for the first time and getting the same issue in Edge. What is the current work around while a more permanent solution is developed? For now,...
I would need the full reproducible source code to troubleshoot this. Please re-open the issue once you provide it.
This library doesn't support the full Telemetry Initializer capabilities. This is due to the fact that JSInterop is async and the Telemetry Initializer callback is synchronous. You can do this...
Thank you, it has been released in 3.1.0.
I attempted to solve this a few times, the main issue is the call is synchronous and JSInterop must be async. I was not able to get this to work...
App Insights calls the telemetryInitializer synchronously, in that method, we need to call JSInterop into Blazor, this call has to be done async. I had it implemented in my v3...