[Feature request] IDE Native Diffs

[dwreeves]

Hi, love the project. We are using it for rich-click and it's vastly improved our test suite.

One thing Claude Code does in its more recent versions is it calls an IDE native view for diffs. Meaning if it detects that I'm using PyCharm, instead of showing diffs in the terminal, it pulls up a window in my editor and shows the diffs there. This not only gives a better visualization of what's changing, it also lets me make adjustments and partial acceptances.

I was thinking it may be useful for changing snapshots to call whatever API Claude Code is calling inside of inline snapshot, so changes use the IDE's native diff view.

Alternatively, or concurrently, the creator of Rich/Textualize has been working on a diff view for AI agents to call. Once this is done it, could be worth looking into adding this for inline_snapshot: https://x.com/willmcgugan/status/1966611338534531515 Diffs in inline_snapshot can be tricky when there are multiple tests per file that are changing because it is tricky to see which diffs corresponds to what test; I basically have to pull up the file and line up the line numbers to see which tests are changing. So a better and more full diff would be extremely helpful.

[15r10nk]

I love that you love the project 😄 .

I'm also thinking about this problem for a while. My idea is to use the lsp to integrate inline-snapshot better in IDEs. This should allow you to approve the changes in your IDE.

• you click the run button in your IDE
• inline-snapshot will show the changes of your snapshots in your IDE.
• you should be able to approve this changes with "some approve button" in your IDE.

This would also solve some aspects of #96.

I plan to release this as an insider feature first like all features which provide no new API's.

And I also know the diff view from Will https://x.com/15r10nk/status/1966464712775733758.

[remimd]

Hello @15r10nk,

I just shared one of my packages on Reddit (pytest-results) and someone recommended your package.

Honestly, I find your package interesting, and the feature requested in this issue is something I will need to potentially use your package in my future projects.

I have implemented this feature in my package, so if you are interested, you can take a look and feel free to ask me if you need any explanation.

[15r10nk]

I think this is the core of your implementation @remimd.

https://github.com/100nm/pytest-results/blob/0b42f4dd0c7ae27066531d187d34e639f3d11f0a/pytest_results/contrib/pytest/plugin.py#L22-L26

This is a really nice approach. Thank you for sharing this with me.

The only problems I see are:

• I have to click "revert" to "approve" changes (I have currently only tested vscode)
• pytests blocks until you closed the tab (which is maybe what we want here, but the user should be told what to do in the terminal)
• And the bigger problem is that I plan to release such features as insider features for my sponsors first. Let me know if this ok for you. I can offer you free insider membership until this feature is part of the non-insider version if you want.

I still think I'll implement an LSP server later, but that's probably much more difficult, and this approach could help in the short term.