Repository navigation
Northwind dashboard: refer to the classes by the names they actually have - #2308
Merged
Merged
Conversation
…have DashboardLayoutAreas referenced OrderViews, SalesViews, SupplierViews and ProductViews. No such classes exist — they are OrderLayoutAreas, SalesLayoutAreas, SupplierLayoutAreas and ProductLayoutAreas, and each already declares the exact member being named. So Northwind/AnalyticsCatalog failed to compile, and Northwind/Product failed after it because Supplier and Category are declared in AnalyticsCatalog's own Source. This is latent on main, not new. In-mesh source compiles at runtime, never in `dotnet build`, and a NodeType keeps its cached bundle until the framework identity changes — so the breakage stays invisible until some change mints a new framework build and every dynamic NodeType recompiles at once. The lift in #2285 does exactly that, which is how this surfaced there rather than here. Behaviour is identical: nameof(X.Y) evaluates to "Y" whatever X is, so all four layout-area names are byte-for-byte what they were. This only repairs the compile. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Fixes a runtime NodeType compilation failure in the Northwind sample analytics dashboard by updating nameof(...) references to match the actual layout-area classes, ensuring Northwind/AnalyticsCatalog (and downstream Northwind/Product) can compile again during in-portal dynamic compilation. Adds a corresponding “What’s New” entry documenting the user-visible impact (dashboard tiles rendering again).
Changes:
- Update
DashboardLayoutAreasto referenceOrderLayoutAreas,SalesLayoutAreas,SupplierLayoutAreas, andProductLayoutAreas(instead of non-existent*Viewstypes) while keeping the resulting layout-area names unchanged. - Add a “What’s New” entry describing the restored Northwind analytics dashboard rendering after the compile fix.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
samples/Graph/Data/Northwind/AnalyticsCatalog/Source/DashboardLayoutAreas.cs |
Corrects nameof(...) type qualifiers to match existing layout-area classes so the NodeType compiles again. |
src/MeshWeaver.Documentation/Data/WhatsNew/2026-08-26-northwind-dashboard-compiles.md |
Documents the fix as a user-visible “Fix” entry for the changelog. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
The samples gate is a one-way ratchet: a listed failure that starts passing fails the run until its line goes, so the list can only shrink. Repairing the stale class names moved the gate from 28/31 to 29/31 NodeTypes compiled, which made 'Northwind/AnalyticsCatalog compile' a stale entry. 'Northwind/Product compile' stays. It is a SEPARATE latent defect of the same class, not a cascade of the first: ProductContent declares [Dimension(typeof(Supplier))] and [Dimension(typeof(Category))], and those records live in AnalyticsCatalog's Source, which Product's NodeType does not reference. Paying that one down means giving Product access to those types — a change to what compiles, not a rename, so it is deliberately not bundled here. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This was referenced Aug 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Northwind/AnalyticsCatalogdoes not compile.DashboardLayoutAreas.csnames four classes that do not exist:OrderViews.OrderSummaryOrderLayoutAreasOrderSummarySalesViews.SalesByCategorySalesLayoutAreasSalesByCategorySupplierViews.SupplierSummarySupplierLayoutAreasSupplierSummaryProductViews.ProductOverviewProductLayoutAreasProductOverviewNorthwind/Productthen fails after it —SupplierandCategoryare declared inAnalyticsCatalog's ownSource/, so a red root makes the dependent red too.Behaviour is identical
All four sites are
nameof(X.Y), which evaluates to"Y"regardless ofX. Every layout-area name passed toControls.LayoutAreais byte-for-byte what it was. This repairs the compile and changes nothing at runtime.This is latent on main, not new
In-mesh source compiles at runtime, never in
dotnet build— and a NodeType keeps its cached bundle until the framework identity changes, at which point every dynamic NodeType recompiles at once. So this breakage is invisible on main and detonates on the first change that mints a new framework build.That is how it surfaced: it turned #2285 (which moves types between assemblies) red, on a gate that is green on
mainwith the identical broken file. Worth noting for anyone reading that red as "#2285 broke Northwind" — it did not; it recompiled it.Verification
Deliberately not verified by
dotnet build:samples/Graph/**is<None>content and is never type-checked by any build or test. TheDoc content compiles and runsgate is the verification, which is where the failure was observed:Expected after this change:
31/31 NodeType(s) compiledwhere the run showed28/31.