Skip to content

Releases: podNET-Hungary/PodNet.Analyzers.Testing

v1.5.3

24 Aug 08:57

Choose a tag to compare

Updated dependencies, moved System.Formats.Asn1 to top-level dependency to force non-vulnerable version.

v1.5.2

16 Aug 12:06

Choose a tag to compare

Added location information to diagnostic message when asserting diagnostics

v1.5.1

16 Aug 08:19

Choose a tag to compare

Added the additional texts as parameters to configuring the compilation for generator testing in EmbeddedTestCase

v1.5.0

15 Aug 18:13

Choose a tag to compare

New feature: TextDiff! This simple helper allows you to visualize line-by-line diffs. Used internally when comparing syntax trees and showing the assertion results.

v1.4.0

15 Aug 15:04

Choose a tag to compare

Added support to configure the generator driver and analyzer options

v1.3.1

15 Aug 12:21

Choose a tag to compare

Replace all underscores with dots in the retrieved property names of embedded test cases. This is to allow better mimicking of the file names the test cases are generated from, and by default, make those look more like files with extensions (eg, Component_razor wouldn't be automatically picked up by a generator if it was looking at extensions). Technically this is a behavioral breaking change, but you can simply pass a new optional parameter or override the property name-value accessor methods on the API to bypass/restore this behavior.

v1.3.0

14 Aug 12:01

Choose a tag to compare

Added support for Additional Texts to provide to generators

v1.2.2

09 Aug 13:47

Choose a tag to compare

Added a certain EmbeddedTestCase that helps with testing complex generator scenarios, including verifying the generated source trees, running scripts inside the generated compilation and running code fixes on them.

There is a small breaking change on PodCSharpCompilation. The first parameter became IEnumerable<SyntaxTree> instead of IEnumerable<string> to allow for greater control over the parameterization (namely, providing file paths to the trees was not possible). If you used the previous version, you can migrate by transforming your source texts to SyntaxTrees by:

sources.Select(s => CSharpSyntaxTree.ParseText(s));

v1.2.1

07 Aug 11:28

Choose a tag to compare

Added sponsorship information

v1.2.0

01 Aug 14:30

Choose a tag to compare

Now the included scripting engine includes by default the same references and namespaces that Visual Studio's Interactive C# REPL includes.