Workflow with JetBrains "Code With Me"?

[CadiChris]

Hi there,

This is more a question than an actual issue.

I've been using Wallby on my own for the past couple of years. On React app through IntelliJ. Everything is perfect.

Current Situation

I've recently joined a team where we use Code With Me to collaborate on a React codebase.

Basically Code With Me gives us access to a shared terminal, so we're back to yarn test in the terminal to have a shared test execution.

This is terribly slow compared to wallaby. I'm really used to blazing speed of Wallaby now 😄

Shared Wallaby execution with "Code With Me"?

I'd like to know if you can think of a solution to have a shared Wallaby execution. I would love to use Wallaby with my whole team. But if I'm the host of the Code With Me session, my local Wallaby execution is not available to my mates.

The first I thought was..."I'd like to start wallaby in the terminal so my mates can see the output" What do you think about that? Is this even remotely possible? Do you have any suggestion on how we could benefit from Wallaby while still using Code With Me?

Discussion much appreciated. Bye !

[smcenlly]

But if I'm the host of the Code With Me session, my local Wallaby execution is not available to my mates.

We've not actually seen the Code With Me experience with Wallaby. We'll try it out later today. My initial thought is that it would be nice for Code With Me to share the editor extensions that Wallaby is already adding (margin glyphs, inline messages, hovers, etc.) without us needing to do anything special (or maybe by simply enrolling our extension as to which features should be shared over a session).

The FAQ for Code With Me says:

Plugins that perform customization of the IDE are supported.

Which I guess should mean that Wallaby should work across sessions. After we do some testing later today, we'll reach out to the JetBrains team and determine what is expected.

[smcenlly]

We had the opportunity to try Code With Me today. Some very limited functionality is available via our tool window icons so it seems like Code With Me is trying to work with Wallaby but virtual nothing works. We have created this issue in JetBrains issue repository to work through the problems with them.

We saw that the Code With Me feature allows you to share local ports with those connected to your session. You may be able to open your Wallaby App and share those ports with people on your session. While not as nice as seeing indicators in your editor, it would allow those connected to see test results and coverage on your code/test files.

[CadiChris]

Thanks a lot for your rapid feedback. I'll try to setup the "share local ports" attempt and see how it goes. Looking forward to hearing from you conversation with JB.

[CadiChris]

If I understand correcly the comment on the JetBrains issue it boils down to

Both host and guest should install Wallaby, and execute it locally. The plugin state will not be shared, but it does not matter: both machines will hopefully see the same tests results since they work on the same code.

I'll let you lead the discussion to avoid polluting it. I'm interested in your understanding though 😄

[EDIT]

TL;DR of the edit 👇 Even after installing Wallaby plugin on the guest Code With Me IDE, we were not able to trigger execution on the guest.

We ran some tests with a mate.

• I'm the host, I have Wallayby plugin installed in my IntelliJ
• He connects to my Code with Me session
• He installs Wallaby plugin in Code with Me IDE and restarts and re-joins the session

We expected him to be able to execute Wallby locally inside his Code With Me IDE... But we could not find a way to start the local execution on his side. 😞 He can only trigger the execution, from his machine through his Run menu, on mine. Which results in the screenshot below: my machine properly exectutes Wallaby and shows full "wallaby UI", his machine only shows the "Run" window, but empty.

[smcenlly]

I'll let you lead the discussion to avoid polluting it. I'm interested in your understanding though 😄

We'll test Quokka and Wallaby today based on their advice and follow up accordingly. We had initially wanted to have the discussion re: Quokka as it's simpler for JetBrains team to get started with and uses a lot of the same underlying concepts (e.g. inline messages, coverage indicators, etc.). If Quokka is running locally instead of on the host machine, then that's not a great outcome.

[CadiChris]

Hi there, I see JetBrains suggested to tweak the Registry. Did you try that ?

[smcenlly]

@cadichris - we didn't try it, we are waiting until inline messages and gutter indicators are supported. Limiting any integration to a mirrored output window only doesn't make any sense to us.