Skip to content

Conversation

@hokolomopo
Copy link
Contributor

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

@robodoo
Copy link
Collaborator

robodoo commented Nov 7, 2025

Pull request status dashboard

@hokolomopo hokolomopo changed the base branch from 19.0 to master November 7, 2025 10:25
@hokolomopo
Copy link
Contributor Author

We can also probably remove the PivotPresencePlugin and the getter/helper getFirstPivotFunction - didn't try yet

@hokolomopo hokolomopo force-pushed the master-pivot-cache-adrm branch from f28927a to 6220c2b Compare November 7, 2025 15:08
Comment on lines +57 to +59
evaluationListenerRegistry.replace("PivotUIPlugin", {
handleEvaluationMessage: this.handleEvaluationMessage.bind(this),
});
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

using a registry is maybe foireux, it will explode if we have multiple models (does it happen in practice ? maybe with dashboard/version history ?)

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.

3 participants