Michael Müller

Thank you for your detailed bug report. Unfortunately, we cannot implement a preview mode for SemanticDiff tabs due to limitations of the VS Code extension API. In an ideal world,...

Thanks for reporting this bug. The issue is actually unrelated to the arrow style function declaration, but has to do with the `async` parameter. The `async` in `(syntax, async)` is...

The issue has been fixed for our GitHub App by switching the C# parser as explained in #66. I will close the issue once the new parser has also been...

As mentioned in #66, the SemanticDiff 0.10.0 release which should fix your issue is now out for VS Code. Please give it a try and report back if it works...

Our diff viewer lacks some features that are available in the standard diff viewer (such as text editing). So we assumed that developers might be more interested in using the...

> On a similar note, the `semanticdiff.closeOriginalTab` setting does not appear to work, though I'm unsure if my VS Code settings or something else is preventing it from seamlessly working...

We just released SemanticDiff 0.10.0 which should fix both of the issues you reported. You can now make SemanticDiff the default diff viewer for all file types by selecting the...

> My last note is that tabs opened by SemanticDiff are not _temporary_: This is already covered by issue #61. The VS Code extension API only supports creating preview tabs...

In the case of your first example this is not an intentional design choice. Our algorithm finds both solutions but considers them equally good and picks one of them. I...

Thanks for your feature request. Can you give me an example of an old and new JSON document that contains such a move? A dummy example or a trimmed down...