Repository navigation
feat(ui): sub-task steps in the task tree; upload page gets a map and citation metadata - #462
Merged
Merged
Conversation
On the problem statement page the open sub-task's steps now nest under its row in the task tree (collapsible, same states, locking and summaries as before) and the middle step-rail column is gone. MintThread derives the step state once and publishes it through onStepNavChange; the stand-alone thread page keeps the rail.
…ummary card The upload page now draws the bounding box on the shared spatial map (a chosen region is outlined on it) with the four coordinate boxes kept under Edit coordinates. It asks for a description and license, and takes tags, source link, version, author, contact email and a line per file, all written to the portal's schema fields. A summary card shows the dataset as others will see it, the chosen variable shows its description and units, and the no-format note from the thread-input check is not shown here. Unlabeled standard variables read as a name instead of a bare id.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Two UI changes the user asked for after #461, in one PR so dev runs a single build.
1. A sub-task's steps sit in the task tree (problem statement page)
/modeling/problem-statement/:id, its steps (Framing … Summary) are listed under it in the task tree, with the same status marks, summaries and locking. The separate "Sub-task steps" column is gone from that page.MintThreadstill owns the step state throughderiveStepStates. A new optionalonStepNavChangeprop publishes it to the embedding page, which rendersSubTaskStepsTree.WizardStepButtonis shared by the rail and the tree./modeling/thread/:id) keepsWizardRailunchanged.2. Upload a dataset: a map, and metadata a reader needs
DatasetSpatialMapreplaces the four coordinate boxes, which remain as a collapsed "Edit coordinates" fallback kept in sync with the map.outline,fitToBox, and labels) are optional and default off, so the thread Datasets step is unchanged.type="button", so they no longer submit a form they sit in.datasetschema fields:notes) and license (license_id, fromlicense_list, defaulting tocc-by).tag_string), source or citation (url), version, author (prefilled with the username) and contact email (maintainer_email, never prefilled).uploadFilesToCatalogparams are optional.Tests
tsc, eslint and prettier clean.🤖 Generated with Claude Code