Charts: add radar charts (chartType "radar")
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
A linked open pull request (#623) is already working on this issue, so check its changes before taking it on. The issue names sdpm/sdpm/engine/builder/elements/chart.py, sdpm/sdpm/engine/converter/chart.py, sdpm/sdpm/engine/schema/lint.py, and the chart guides and tests. Done means radar charts build and round-trip with markers and data intact, lint accepts the type, and the listed lint and pytest commands pass.
Written by the indexing model from the issue text.
Description
What problem would this solve?
Native charts support chartType bar, line, pie and donut only. Radar (spider) charts are a common way to compare options across several criteria (vendor evaluation, skill maps, Well-Architected pillar scores), and python-pptx builds them natively (XL_CHART_TYPE.RADAR, RADAR_MARKERS). Today an agent has to approximate them with a bar chart, and a radar chart imported with pptx_to_json is read as a bar chart that only its _chartXml keeps (_chartRebuildable: false).
Proposed solution
Add chartType: "radar". It uses the same category data as line, and the existing markers flag:
{
"type": "chart", "chartType": "radar",
"x": 192, "y": 216, "width": 1000, "height": 700,
"categories": ["Cost", "Performance", "Security", "Reliability", "Operations"],
"series": [
{"name": "Option A", "values": [4, 3, 5, 4, 2], "color": "#FF9900"},
{"name": "Option B", "values": [2, 5, 3, 3, 4], "color": "#41B3FF"}
],
"markers": true,
"legend": true,
"valueAxis": {"min": 0, "max": 5, "majorUnit": 1}
}
markers: true(default, as forline) →XL_CHART_TYPE.RADAR_MARKERS,markers: false→XL_CHART_TYPE.RADAR. The filled variant (RADAR_FILLED) is out of scope and stays non-rebuildable.- Series
coloris the line (and marker) colour, as forline;style.lineWidth/style.markerSizeapply. valueAxis(min/max/majorUnit/gridlines) sets the radial scale.
Files to touch:
sdpm/sdpm/engine/builder/elements/chart.py(_add_chart): thetype_map; the series colour branch (elif chart_type == "line"— radar series are lines too); check that the "Axis & gridline styling (bar/line only)" block works on a radar chart's axes, or skip the parts that do not apply.sdpm/sdpm/engine/converter/chart.py(extract_chart_element): mapRADAR/RADAR_MARKERSintype_map(andmarkers: falsefor plainRADAR, likeLINE), so the chart reads back asradarand becomes rebuildable.sdpm/sdpm/engine/schema/lint.py: addradarto_CHART_TYPESand update the "Specify bar, line, pie, or donut" message.- Docs: the chart section of
sdpm/references/guides/slide-json-media.md(chartTypelist and guide list), and a newsdpm/references/guides/chart-radar.mdmodelled onchart-line.md(when to use it: few series, 3–8 criteria on the same scale). If you add the guide, also add it next tochart-bar/chart-line/chart-pieinsdpm/references/guides/slide-json-spec.mdandsdpm/references/workflows/composer.md. CHANGELOG.md: an entry under[Unreleased]→Added.
Done when
-
chartType: "radar"builds ac:radarChart(with and without markers), andpptx_to_jsonreads it back aschartType: "radar"withmarkers, categories, series names, values and colours intact. - An edited radar chart is rebuilt from its JSON: drop
"radar"from thekindlist ofTestChartsTheJsonCannotDescribe::test_edited_chart_keeps_its_typeintests/test_chart_roundtrip.py. - Lint accepts
radarand still rejects unknown types. -
make lintanduv run pytest tests/test_chart_roundtrip.py -vpass.
Tests to copy: TestChartTypes::test_line_markers and TestColors::test_line_series_color in tests/test_chart_roundtrip.py (they use _one_chart / _built_chart, no LibreOffice needed).
Which area?
Slide generation / engine (layouts, elements, charts)
🤖 Created by Kiro Crew
- Dominant language
- Python
- Stars
- 136
- Forks
- 13
- Avg merge
- 7h 43m
- Merged PRs (30d)
- 180
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aws-samples/sample-spec-driven-presentation-maker
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
aws-samples/sample-spec-driven-presentation-maker#648 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
aws-samples/sample-spec-driven-presentation-maker#646 ·
Maintainers usually reply within 1 day
-
Charts: setting `valueAxis` skips theme styling of axis labels and axis linesPossibly taken @ShotaroKataoka claimed this 1 day ago. Openbug
Difficulty 3/5 1-2 days Newbie friendliness 67/100
aws-samples/sample-spec-driven-presentation-maker#630 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 50/100
aws-samples/sample-spec-driven-presentation-maker#627 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 4/5 3-5 days Newbie friendliness 68/100
aws-samples/sample-spec-driven-presentation-maker#622 ·
Maintainers usually reply within 1 day
All issues in aws-samples/sample-spec-driven-presentation-maker
Similar issues
-
firestore: enable live window.yaml pipeline system tests once add_window_fields is in productionOpen
Difficulty 1/5 Under an hour Newbie friendliness 64/100
googleapis/google-cloud-python#19115 ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug prov-json
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 1 day