Skip to content

Conversation

@jgallagher
Copy link
Contributor

Tiny cleanup opportunity I noticed while implementing #9496 - we don't need to store a separate "most recently loaded" field (and keep it in sync with our watch channel) because we can just look in the watch channel.

Staged on top of #9496.

@jgallagher jgallagher force-pushed the john/loaded-blueprint branch from 8816932 to 9d7e1da Compare December 11, 2025 21:21
Tiny cleanup opportunity I noticed while implementing #9496 - we don't
need to store a separate "most recently loaded" field (and update it in
sync with our watch channel) because we can _just look in the watch
channel_.
@jgallagher jgallagher force-pushed the john/blueprint-loader-no-last branch from 5990fd2 to 9adef9a Compare December 11, 2025 21:22
Base automatically changed from john/loaded-blueprint to main December 12, 2025 15:20
@jgallagher jgallagher merged commit 474c158 into main Dec 12, 2025
16 checks passed
@jgallagher jgallagher deleted the john/blueprint-loader-no-last branch December 12, 2025 18:25
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.

3 participants