feat(explorer): scenario filter — ?scenario= reads the forecast slice#223
Merged
Conversation
ScenarioSelect in the Block Explorer header (visible once the graph has a forecast block): 'Actuals' reads the null scenario; picking a scenario threads its structure id through every envelope read — the metric series extends with '(forecast)'-labeled columns, statements bind the latest computed month. State is URL-encoded (?block/?view/?scenario) so a scenario view is shareable. BlockView renders forecast blocks (the authored lever container) through the metric projection — the server shapes the lever grid metric-style, so no new renderer. MetricRendering/StatementRendering already prefer period.label, so the forecast column labels display without changes. Requires @robosystems/client with scenario-aware reads (the getInformationBlock options arg) — verified against the local build; the dependency bump lands with the next client publish.
The published client carrying the F-1 scenario surface — the getInformationBlock/listInformationBlocks scenarioId options this branch's explorer filter requires. Full gate re-verified against the published package (one deduped copy in the tree), not a local build.
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
1 participant
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.
Summary
Frontend tail of robosystems#917 (the F-1 forecast engine).
?block/?view/?scenario) so a scenario view is shareable.period.label, so forecast column labels display with zero changes.Verification
npm run test:allgreen against the local @robosystems/client build (the newgetInformationBlockoptions arg), incl. a new?scenario=threading test.Sequencing
Blocked on the @robosystems/client publish from typescript-client#154 — a follow-up commit on this branch bumps the dependency + lockfile once it's on npm; CI will be red until then. Merge order: robosystems#917 deploy → client publish → bump → merge here.