Ricardo Montoya

Any news about this feature request? Is it viable or it's something totally out of consideration for the rest of the year at least?

@wayou Yes. The problem occurs just by installing/enabling the extensión with its default settings. I didn't touch any of them. As I described when I opened the issue, I made...

It's globally installed. ``` $ watchman -v 4.7.0 ```

hi @andrew-ironforge @vladoro did you solved your problem? I'm having > "Could not connect to websocket endpoint ws://:/graphql. Please check if the endpoint url is correct.". Same occurs whe using...

> @mogarick no I never fixed my problem. I think we are having different issues though because your URL does not look valid. Sorry @andrew-ironforge , it looks the url...

I can add that when using `entry:log("something")` nothing gets rendered. It only happens for the `entry` that belongs to the initial state. So in the @smarko82 example, if I use...

One more thing, using ``` entry:{ actions: log("something")} ``` causes a blank screen on the stately.ia visualizer page: `Application error: a client-side exception has occurred (see the browser console for...

ok. give me a minute then...

entry:log("something) entry:{actions:log("something")} this last one shows "anonymous" for the entry, and with such value in the visualizer it throws the `a client-side...` error. in the case of the vs-code extension,...

Got it. I can confirm using `entry:log("Entered signIn NavState)` or `entry: [log("Entered signIn NavState")],` works on the website visualizer. But then the problem is on the vs-code extension visualizer. Using...