Skip to content

Conversation

@rrahir
Copy link
Collaborator

@rrahir rrahir commented Dec 24, 2025

Description:

The command UPDATE_CELL was designed so that any style passed to it
would simply overwrite the cell style. This differs from the
SET_FORMATTING command and unfortunately, the distinction was lost
during recent split of style from the cells.

Task: 5441149

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

The mock transport service did not serialize the messages which means we
do not properly mock the actual behaviour.

Task: 5441149
The command UPDATE_CELL was designed so that any style passed to it
would simply overwrite the cell style. This differs from the
SET_FORMATTING command and unfortunately, the distinction was lost
during recent split of style from the cells.

Task: 5441149
@robodoo
Copy link
Collaborator

robodoo commented Dec 24, 2025

Pull request status dashboard

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