I don't think the parinfer experiment is included? The changelog must have still been messy.

The handling for unknown-op commands might start to surface more errors to users that were silently ignored in the past. The most helpful should be that we now get an error saying “the server couldn't handle the test-all command”

The best step there will be to somehow help the user ensure that cider-nrepl middleware is installed.

We should consider checking for cider-nrepl middleware somewhere early in the REPL lifecycle and help the user there. And possibly have a context variable we can check before enabling commands that rely on it.

Which wallpaper?

I get this at normal maximisation

Interesting. Never seen it before. Which version of Chrome are you using?

95.0.4638.69

on mac

Maybe just a failed resource download? What if you reload it w/o caches?

hmm you might be right - can't quite load the page with incognito

That sound very strange!

If you have cache disabled when the dev tools are showing, that’s one way to load it w/o cache. You can also long-press on the reload button to get options for hard reload.

Nahhhh 😅 just restrictions on my work machine ><

Apparently it is cause there are 3rd party cookies ?

Google analytics is the only thing going on there that involves 3p cookies.

Hmmmm, but regardless I guess it isn't any issue of calva's. Just the many restrictions my company imposes 😅

Not yet. Please file an issue. Should be easy to add.

Thanks, will do.

(I didn’t see any unit tests in the repo)

For the TS code there are two kinds of tests, unit and integration tests (actually there is just one integration test). If the tests require vscode to be imported then the integration tests is what can be used. What I tend to do is factor things so that I can test them w/o vscode. You’ll find both categories in src/extension-test

perfect, thanks!

If you do add some integration tests, that would be awesome. It has been there for quite a while, but no-one has bothered with adding any interesting tests. They are run in CI, so it is probably good to have a few such tests.

But that is more FYI and for future efforts.

https://github.com/BetterThanTomorrow/calva/pull/1402/files#diff-263442184ee9e4abf642adacab026def2cd34f0cfe3631876347ab5fe4c65febR17

I’ve written my first tests 💪

Who! That’s great!

(testing "Peter's emoji continue to work")

😄

Haha!

If you think there is clearer way to show results, please suggest. 😃

I think that some of the data in this messages could become redundant once we wire up the native Test Explorer.

It’s a VS Code command: Format Document

cool, I was looking for Calva: format something :)

It’s a common source of confusion. In this particular instance VS Code has the command and Calva provides the mechanics. VS Code does not have a Format Current Form command, though, so that is a Calva command. 😃

Also: If you have the cursor at the top level and issue the Calva: Format Current Form command, the entire buffer will be formatted. ¯\(ツ)/¯

Can you also format on save?

You can enable it, but I think it might be a bit erratic. Iirc VS Code only allows a certain time for it. But I could be wrong.

I always forgot that Format Document command as well 😂

Dart-Code extension (LSP for Dart/Flutter), has format on save feature, and it's something community really likes, even emacs users (lsp-dart)

@U01EB0V3H39 May also be worth asking in #portal -- I don't know of anyone using nREPL with the Portal extension (I use a Socket REPL) but maybe someone in the Portal channel can help.

I have it working. Can you describe the steps you take?

@U0ETXRFEW could it be because @U01EB0V3H39 is running the REPL inside a Docker container?

Yes, I imagine that could take some extra setup. Maybe try without that and see if that works?