Repository navigation
Release v4.107.0
Summary
The first-run scaffold now produces a Cratis application a developer recognizes: a separate specifications project, central package management, real build properties and a README.
Added
- The scaffold emits a
<Project>.Specsproject next to the web project. It compiles the generated slice specifications in place, so slice files keep their paths, and runs them withdotnet test. (part of #401) - The scaffold enables central package management:
Directory.Packages.propspins every package version and the projects reference packages without versions. (part of #401) - The scaffold's
Directory.Build.propssets nullable reference types, the latest C# version, warnings as errors and code-style enforcement for every project, and an.editorconfigthat allows specification-style names in specifications. NuGet's machine-dependent restore warnings (NU1507,NU1900–NU1904) stay warnings. (part of #401) - The scaffold adds a
README.mdwith run instructions for Chronicle, the backend, the frontend and the specifications. (part of #401)
Changed
- A generated application ignores
.editorconfigand.globalconfigfiles in parent folders, so it builds the same inside another repository. (part of #401)