Skip to content

Chore/validate purview 2026 10 - #147

Merged
kieronlanning merged 2 commits into
mainfrom
chore/validate-purview-2026-10
Oct 22, 2026
Merged

kieronlanning merged 2 commits into
mainfrom
chore/validate-purview-2026-10

Conversation

@kieronlanning

Copy link
Copy Markdown
Contributor

No description provided.

The TelemetryNames class stage combined resolvedNames with CompilationProvider, putting a Compilation
into a cached pipeline value. A Compilation is compared by reference and is a new instance on every
keystroke, so that stage could never report cached and everything downstream recomputed every time.

The referenced assemblies names and this assembly name are now projected into a value-equatable
ReferencedTelemetryNamesContext before they reach a cached node, which is the pattern
assemblyNameProvider and assemblySettings already use in the same method.

Collect now runs for every compilation rather than only when the aggregated class is generated. That
is the cost of keeping the Compilation out of cached state, and a net win: the previous shape
recomputed that stage and everything below it unconditionally.

Flagged by PSGFR33 in Purview.SourceGeneratorFramework 1.2.0.

Takes Purview.BuildSdk 1.1.0, Purview.Build 0.7.0, Purview.SourceGeneratorFramework 1.2.0 and
Purview.Skills.Testing 1.1.0.
@kieronlanning
kieronlanning merged commit 5e13bad into main Oct 22, 2026
2 checks passed
@kieronlanning
kieronlanning deleted the chore/validate-purview-2026-10 branch October 22, 2026 12:02
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