fix: Data browser graph requires value field even when calculated value is defined

[mtrezza]

New Pull Request Checklist

• I am not disclosing a vulnerability.
• I am creating this PR in reference to an issue.

Summary by CodeRabbit

• New Features
  • Charts can now use calculated values as data sources, offering an alternative to value columns for pie, doughnut, bar, line, and radar chart types. Enhanced validation ensures proper configuration with either data source.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[parse-github-assistant]

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

[coderabbitai]

📝 Walkthrough

Walkthrough

Changes relax chart configuration validation to support calculated values as an alternative to valueColumn. Updated functions now permit pie/doughnut and bar/line/radar charts to use either valueColumn or calculatedValues as valid data sources, enabling more flexible chart creation.

Changes

Cohort / File(s)	Summary
Chart Validation Enhancement src/dashboard/Data/Browser/GraphDialog.react.js, src/lib/GraphDataUtils.js	Relaxed input validation in processPieData, processBarLineData, and validateGraphConfig to accept either valueColumn or calculatedValues as valid data sources for pie/doughnut and bar/line/radar charts. Introduced hasCalculatedValues and hasValuesToDisplay helper checks to determine chart validity. Updated GraphDialog.valid() to consider calculated values when validating configurations.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete. The checklist is partially filled but critical sections like Issue Description, Approach, and TODOs are missing or only contain placeholder text.	Complete the description by adding the issue reference in 'Closes:' field, describing the approach to fixing the validation logic, and noting any TODOs before merging.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main fix: allowing calculated values to satisfy graph validation requirements instead of requiring a value field.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[parseplatformorg]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[parseplatformorg]

🎉 This change has been released in version 8.3.0-alpha.10