Skip to content

Conversation

@LucasLefevre
Copy link
Collaborator

Description:

description of this task, what is implemented and why it is implemented that way.

Task: TASK_ID

review checklist

  • feature is organized in plugin, or UI components
  • support of duplicate sheet (deep copy)
  • in model/core: ranges are Range object, and can be adapted (adaptRanges)
  • in model/UI: ranges are strings (to show the user)
  • undo-able commands (uses this.history.update)
  • multiuser-able commands (has inverse commands and transformations where needed)
  • new/updated/removed commands are documented
  • exportable in excel
  • translations (_t("qmsdf %s", abc))
  • unit tested
  • clean commented code
  • track breaking changes
  • doc is rebuild (npm run doc)
  • status is correct in Odoo

Currently, 'humanize' is not explicitely set when creating a new chart.
The default value `true` is later assigned as a fallback in the Chart
class.
I'd like to simplify those classes.
`data` was typed as `any`.
This is not a good thing in itself.
Moreover, it was only the values without the format.
Also typeof is extremely permissive
The format of chart axis no longer depends on ranges, but now on the chart
data.
This getter is only used once and the formatted values can be taken from
the evaluated cells without the need to iterate over the entire range again.
The goal is ultimately to get the format from there
instead of using the label range and reading again
the cells (see next commit)
Extract chart data from ranges is now decoupled from everything else
@robodoo
Copy link
Collaborator

robodoo commented Dec 3, 2025

Pull request status dashboard

@LucasLefevre LucasLefevre force-pushed the master-chart-extract-data-4-lul branch from 219a4db to 4bcf288 Compare December 3, 2025 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants