Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FIX] sheet: Avoid divergent sheet names in collaborative #5090

Closed
wants to merge 1 commit into from

Conversation

rrahir
Copy link
Collaborator

@rrahir rrahir commented Oct 14, 2024

Similar issue to the one raised in #5010. If 2 userrs with different languages (i.e. different translation schemes), importing a sheet data without a name could result in different outcomes for both users.

Currently, this is not an issue because the sheet data are 'fixed' upstream by the migration mecanism but this might change/disappear in the future.

Task: 0

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

Similar issue to the one raised in #5010.
If 2 userrs with different languages (i.e. different translation
schemes), importing a sheet data without a name could result in
different outcomes for both users.

Currently, this is not an issue because the sheet data are 'fixed'
upstream by the migration mecanism but this might change/disappear in
the future.

Task: 0
@robodoo
Copy link
Collaborator

robodoo commented Oct 14, 2024

Pull request status dashboard

Copy link
Collaborator

@LucasLefevre LucasLefevre left a comment

Choose a reason for hiding this comment

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

robodoo r+

robodoo pushed a commit that referenced this pull request Oct 14, 2024
Similar issue to the one raised in #5010.
If 2 userrs with different languages (i.e. different translation
schemes), importing a sheet data without a name could result in
different outcomes for both users.

Currently, this is not an issue because the sheet data are 'fixed'
upstream by the migration mecanism but this might change/disappear in
the future.

closes #5090

Task: 0
Signed-off-by: Lucas Lefèvre (lul) <[email protected]>
@robodoo robodoo closed this Oct 14, 2024
@robodoo robodoo added the 18.1 label Oct 14, 2024
@fw-bot fw-bot deleted the master-collaborative-sheetname-rar branch October 28, 2024 09:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants