refactor: align adventure YAML schema with challenges repo format#77
Merged
Conversation
Renames and restructures all adventure YAML fields to match the
challenges repo conventions, so the automation that creates PRs from
new challenges can write valid YAML with minimal transformation:
- `id` -> `slug`, `title` -> `name`, `tags` -> `technologies` (YAML only; generator still outputs `id`/`title`/`tags` to TypeScript)
- `context: {title, body}` -> `overview: string[]`; section heading hardcoded as "Overview" in AdventureDetail
- Deadlines converted from human-readable strings to ISO 8601 across all 12 levels and adventure-level rewards
- All `how_to_play` step fields renamed `body` -> `content`; `helpful_links` item field `label` -> `title` with optional `description`
- All multi-word YAML fields are now snake_case: `how_to_play`, `helpful_links`, `devcontainer_path`, `discussion_url`, `architecture_diagram`, `diagram_alt`, `meta_description`, `solved_count`, `top_players`, `upcoming_levels`, `ranking_note`, `ranking_rules_url`
- `services` field added to every level; generator auto-inserts "Explore the UIs" walkthrough step from service list
- `icon` field added at adventure level (Lucide icon name); rendered after the title in AdventureDetail header
- `architecture_ascii` added as optional fallback; ArchitectureSection now renders SVG > ASCII > text in priority order
- `isDeadlinePast` simplified to native ISO parsing; new `formatDeadline` formats ISO strings for display
- All tests, fixtures, and styleguide.md updated to match new field names
Signed-off-by: Sinduri Guntupalli <sinduri.g@gmail.com>
Signed-off-by: Sinduri Guntupalli <sinduri.guntupalli@dynatrace.com>
Contributor
|
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.
Renames and restructures all adventure YAML fields to match the challenges repo conventions, so the automation that creates PRs from new challenges can write valid YAML with minimal transformation:
id->slug,title->name,tags->technologies(YAML only; generator still outputsid/title/tagsto TypeScript)context: {title, body}->overview: string[]; section heading hardcoded as "Overview" in AdventureDetailhow_to_playstep fields renamedbody->content;helpful_linksitem fieldlabel->titlewith optionaldescriptionhow_to_play,helpful_links,devcontainer_path,discussion_url,architecture_diagram,diagram_alt,meta_description,solved_count,top_players,upcoming_levels,ranking_note,ranking_rules_urlservicesfield added to every level; generator auto-inserts "Explore the UIs" walkthrough step from service listiconfield added at adventure level (Lucide icon name); rendered after the title in AdventureDetail headerarchitecture_asciiadded as optional fallback; ArchitectureSection now renders SVG > ASCII > text in priority orderisDeadlinePastsimplified to native ISO parsing; newformatDeadlineformats ISO strings for display