Skip to content

3.0.1

Choose a tag to compare

View all tags
@DylanSnel DylanSnel released this 01 Oct 15:45
v3.0.1
9449912
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

DDD_Module now reaches the generators wherever they run. Nothing changes for a project that references Temp.DDDToolkit. A project that references only Temp.DDDToolkit.Abstractions and Temp.DDDToolkit.Analyzers gets the names it asked for after the update. The changelog has the full entry.

Fixed

DDD_Module was ignored in a project that had the generators without the DDDToolkit package. The property was declared to the compiler by a props file in DDDToolkit, while the generators that read it ship in DDDToolkit.Analyzers. Two setups were affected, and in both {Module}EventNames was named after the assembly without a word:

  • A contracts project that references DDDToolkit.Abstractions and DDDToolkit.Analyzers.
  • A project that gets the toolkit through a project reference.

DDDToolkit.Analyzers now carries the props file itself, in build/ and in buildTransitive/. See DDD_Module, and the package that brings it.

Added

  • DDD00014, a warning for a project the generators run in while the props file was not imported, for example because the reference excludes the package's build assets. DDD_Module is ignored there, and the build now says so.
  • Referencing DDDToolkit.Abstractions and DDDToolkit.Analyzers without DDDToolkit is a supported setup, built against the packed packages on every pull request.

Package ids

3.x is still published as Temp.DDDToolkit.*:

dotnet add package Temp.DDDToolkit --version 3.0.1
Assets 2
Loading