Fix up wiki docs within GitHub#348
Merged
lhawkman27 merged 6 commits intoMar 20, 2026
Merged
Conversation
- Fix 9 broken internal wiki links across Home, Getting-Started, GeoSet-Map-Layer, and GeoSet-Multi-Map pages (removed "Chart" suffix and corrected "Sample Data and Demo Dashboards" to "Sample Dashboards") - Update wiki screenshots with current UI images - Fix defaultLegendName/defaultLegendNames mismatch: frontend was reading plural "defaultLegendNames" but schema uses singular "defaultLegendName", causing the feature to silently not work - Update GeoSet-Map-Layer.md: move pointSize out of globalColoring (V4), add dynamic pointSize docs, update range to 1-200, list all pointType values - Clarify PR raft-tech#319 TODO note in JSON-Config-Spec.md Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add a complete example section to the JSON Config Spec wiki page showing all configuration fields together. Also fix H1 titles in three wiki pages to match their filenames and cross-link targets. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
2 participants
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
defaultLegendNames→defaultLegendNameJSON key in frontend code to match backend schemapointSizedocumentation (static and dynamic data-driven) to GeoSet Map Layer wikiFocus Score
8/10 — All changes are documentation and wiki-related fixes, with one small bug fix (
defaultLegendNamekey rename) that is directly tied to the documentation updates. The scope is tightly focused on making wiki docs accurate and consistent.Detailed Summary of Each File Changed
wiki/Home.md— Updated page links to use new wiki page names (dropped "Chart" suffix, renamed Sample Dashboards); replaced hero screenshotwiki/Getting-Started.md— Updated "Next Steps" wiki links to match renamed pageswiki/GeoSet-Map-Layer.md— Fixed H1 title, updated cross-links, replaced screenshots, addedpointSizesection (static & dynamic), expandedpointTypeicon list, movedpointSizeout ofglobalColoring, fixed table formattingwiki/GeoSet-Multi-Map.md— Fixed H1 title, updated all cross-links to renamed pages, replaced screenshotswiki/Sample-Dashboards.md— Fixed H1 title to "Sample Dashboards", updated screenshots, fixed markdown table alignmentwiki/JSON-Config-Spec.md— Added "Complete Example" section with full config sample, restructured TOC with proper nesting, fixed table column alignmentsuperset-frontend/.../GeoSetLayer.tsx— RenameddefaultLegendNames→defaultLegendNameJSON key access to match backend schemasuperset-frontend/.../transformProps.ts— SamedefaultLegendNames→defaultLegendNamekey renameTest Plan
[[wiki links]]resolve to the correct pagescolorByCategoryconfig containingdefaultLegendNamekey to ensure legend labels render correctlydefaultLegendNamestill fall back to['Other']🤖 Generated with Claude Code