Add the other packages to the release. Update the docs to explain the different packages.

Author: leeoades

.github/workflows/release.yml

@@ -21,13 +21,19 @@ jobs:
           dotnet-version: "9.0.x"
 
       - name: Restore
-        run: dotnet restore FunctionalStateMachine.Core/FunctionalStateMachine.Core.csproj
+        run: dotnet restore FunctionalStateMachine.sln
 
       - name: Build
-        run: dotnet build FunctionalStateMachine.Core/FunctionalStateMachine.Core.csproj --configuration Release --no-restore
+        run: dotnet build FunctionalStateMachine.sln --configuration Release --no-restore
+
+      - name: Set Version
+        run: echo "VERSION=${GITHUB_REF_NAME#v}" >> $GITHUB_ENV
 
       - name: Pack
-        run: dotnet pack FunctionalStateMachine.Core/FunctionalStateMachine.Core.csproj --configuration Release --no-build --output ./artifacts --include-symbols --include-source
+        run: |
+          dotnet pack FunctionalStateMachine.Core/FunctionalStateMachine.Core.csproj --configuration Release --no-build --output ./artifacts --include-symbols --include-source /p:PackageVersion=${VERSION}
+          dotnet pack FunctionalStateMachine.CommandRunner/FunctionalStateMachine.CommandRunner.csproj --configuration Release --no-build --output ./artifacts --include-symbols --include-source /p:PackageVersion=${VERSION}
+          dotnet pack FunctionalStateMachine.Diagrams/FunctionalStateMachine.Diagrams.csproj --configuration Release --no-build --output ./artifacts --include-symbols --include-source /p:PackageVersion=${VERSION}
 
       - name: Release
         uses: softprops/action-gh-release@v2

Directory.Build.props

@@ -0,0 +1,5 @@
+<Project>
+  <PropertyGroup>
+    <PackageVersion Condition="'$(PackageVersion)' == ''">0.0.0-dev</PackageVersion>
+  </PropertyGroup>
+</Project>

FunctionalStateMachine.CommandRunner.Generator/FunctionalStateMachine.CommandRunner.Generator.csproj

@@ -7,6 +7,7 @@
     <IsRoslynAnalyzer>true</IsRoslynAnalyzer>
     <EnforceExtendedAnalyzerRules>true</EnforceExtendedAnalyzerRules>
     <NoWarn>$(NoWarn);RS1035</NoWarn>
+    <IsPackable>false</IsPackable>
   </PropertyGroup>
 
   <ItemGroup>

FunctionalStateMachine.sln

@@ -27,6 +27,7 @@ Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "_", "_", "{919D74CB-8078-40
 		docs\internal-transitions.md = docs\internal-transitions.md
 		docs\no-data.md = docs\no-data.md
 		docs\state-data.md = docs\state-data.md
+		docs\packages.md = docs\packages.md
 	EndProjectSection
 EndProject
 Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "FunctionalStateMachine.CommandRunner", "FunctionalStateMachine.CommandRunner\FunctionalStateMachine.CommandRunner.csproj", "{A0A6A44F-CD8C-49F6-B659-5BA7B77A2BB4}"

README.md

@@ -70,6 +70,7 @@ var (nextState, nextData, commands) = machine.Fire(new LightTrigger.Toggle(), cu
 
 Each feature has its own short guide with simple and more advanced examples.
 
+- Packages and when to reference them: [docs/packages.md](docs/packages.md)
 - Commands instead of side effects: [docs/commands-vs-effects.md](docs/commands-vs-effects.md)
 - Fluent configuration: [docs/fluent-configuration.md](docs/fluent-configuration.md)
 - Entry and exit commands: [docs/entry-exit.md](docs/entry-exit.md)
@@ -86,4 +87,3 @@ Each feature has its own short guide with simple and more advanced examples.
 ## Additional
 
 - See Samples in `FunctionalStateMachine.Samples` project.
-

docs/index.md

@@ -4,6 +4,7 @@ Welcome to the Functional State Machine docs. Each guide introduces a feature, w
 
 ## Core features
 
+- Packages and when to reference them: `packages.md`
 - Commands instead of side effects: `commands-vs-effects.md`
 - Fluent configuration: `fluent-configuration.md`
 - Entry and exit commands: `entry-exit.md`

docs/packages.md

@@ -0,0 +1,35 @@
+# Packages
+
+This library is split into a few packages so you can reference only what you need.
+
+## FunctionalStateMachine.Core
+
+The core state machine implementation. 
+Most consumers should reference this package otherwise what are you even doing here? 🤣
+
+## FunctionalStateMachine.CommandRunner
+
+Optional command runner integration that dispatches commands through DI.
+You can implement your own command dispatcher but it's very boilerplate-y.
+
+Use it when you want:
+- Command handlers as DI-resolved classes.
+- A built-in provider to run commands returned by the state machine.
+
+Note: It includes a source generator so the disptacher does not use reflection.
+
+## FunctionalStateMachine.Diagrams
+
+Design-time diagram generator for Mermaid diagrams.
+
+Use it when you want:
+- Build-time diagrams from your builder methods.
+- No runtime dependency (analyzer-only package).
+
+Add a package reference and annotate builder methods with `[StateMachineDiagram("path/to/diagram.md")]`.
+
+## Quick reference
+
+- Always: `FunctionalStateMachine.Core`
+- Optional: `FunctionalStateMachine.CommandRunner` for DI-based command execution.
+- Optional: `FunctionalStateMachine.Diagrams` for build-time Mermaid diagrams.