Skip to content

feat: use SiteMappingDescription from EssentialCSharp.Shared.Models - #1560

Merged
BenjaminMichaelis merged 1 commit into
mainfrom
feat/use-shared-site-mapping-description
Oct 24, 2026
Merged

BenjaminMichaelis merged 1 commit into
mainfrom
feat/use-shared-site-mapping-description

Conversation

@BenjaminMichaelis

Copy link
Copy Markdown
Member

Summary

  • Bumps ToolingPackagesVersion 1.1.1.19562 -> 1.1.1.19570, which adds SiteMappingDescription (IntelliTect-dev/EssentialCSharp.Tooling#2605).
  • ChapterDescriptionService now deserializes sitemap.descriptions.json into the shared SiteMappingDescription instead of a private ChapterDescription record, so the tooling and web app share one type, like SiteMapping.
  • JSON shape is unchanged.

Test plan

  • dotnet build EssentialCSharp.Web.slnx
  • ChapterDescriptionServiceTests (2 pass)

Bump the tooling packages to 1.1.1.19570 and replace the private
ChapterDescription record with the shared SiteMappingDescription type
that the tooling serializes.
@BenjaminMichaelis
BenjaminMichaelis merged commit 72d1350 into main Oct 24, 2026
21 checks passed
@BenjaminMichaelis
BenjaminMichaelis deleted the feat/use-shared-site-mapping-description branch October 24, 2026 01:10
BenjaminMichaelis added a commit that referenced this pull request Oct 24, 2026
## Summary
- Bumps `ToolingPackagesVersion` 1.1.1.19570 -> 1.1.1.19573.
- 19570's content package shipped `sitemap.descriptions.json` with the
old single-string `"Key"` format, which `SiteMappingDescription` (used
by `ChapterDescriptionService` since #1560) cannot deserialize, so dev
returned 500. 19573 is built from
IntelliTect-dev/EssentialCSharp.Tooling#2606, which converts the file to
the `Keys` array format and adds a tooling test that reads the real
file.

## Test plan
- [x] `dotnet build EssentialCSharp.Web.slnx`
- [x] `EssentialCSharp.Web.Tests`: 190 passed
- [x] At the tooling commit 19573 was built from (1f77290e),
`sitemap.descriptions.json` has 589 `"Keys"` entries and no `"Key"`
entries
- [ ] Not checked locally: the restored ContentFeedNuget package
contents. Please confirm dev serves pages after deploy.

Related: #1561 (Key/Keys compatibility and CI check against the real
package content) is still open and no longer needed to fix dev once this
is deployed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant