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] Selection: Loop selection based on content #3573

Closed
wants to merge 1 commit into from

Conversation

rrahir
Copy link
Collaborator

@rrahir rrahir commented Jan 30, 2024

Similarly to the issue addressed in PR #3214, we want loopSelection to consider seemingly empty cells when considering the expansion zone.

This revision splits the behaviour of the selection processor for loopSelection and the other navigation features (like cluster jumping) as we still want to ignore cells with an empty evaluation in those cases. The reason being that the user could be lost if, when navigating with their keyboards, they end up with their selection on empty cell.

As for #3214, the fix will need to be adapted to account for the spreaded formulas.

Task: 3709340

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

Similarly to the issue addressed in PR #3214, we want `loopSelection`
to consider seemingly empty cells when considering the expansion zone.

This revision splits the behaviour of the selection processor for
`loopSelection` and the other navigation features (like cluster
jumping) as we still want to ignore cells with an empty evaluation in
those cases. The reason being that the user could be lost if, when
navigating with their keyboards, they end up with their selection on
empty cell.

As for #3214, the fix will need to be adapted to account for the
spreaded formulas.

Task: 3709340
@rrahir rrahir force-pushed the saas-16.1-emptycell-not-cellvalue-rar branch from ce0f61d to c03cbf2 Compare January 30, 2024 18:25
@robodoo
Copy link
Collaborator

robodoo commented Jan 30, 2024

@rrahir
Copy link
Collaborator Author

rrahir commented Jan 30, 2024

@fw-bot up to saas-16.3

@fw-bot
Copy link
Collaborator

fw-bot commented Jan 30, 2024

Forward-porting to 'saas-16.3'.

rrahir added a commit that referenced this pull request Jan 31, 2024
Similarly to the issue addressed in PR #3214, we want `loopSelection`
to consider seemingly empty cells when considering the expansion zone.

This revision splits the behaviour of the selection processor for
`loopSelection` and the other navigation features (like cluster
jumping) as we still want to ignore cells with an empty evaluation in
those cases. The reason being that the user could be lost if, when
navigating with their keyboards, they end up with their selection on
empty cell.

This PR is the adaptation of #3573 to support cells that contain the
result of a spreaded formula.

Task: 3709340
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 Feb 9, 2024
Similarly to the issue addressed in PR #3214, we want `loopSelection`
to consider seemingly empty cells when considering the expansion zone.

This revision splits the behaviour of the selection processor for
`loopSelection` and the other navigation features (like cluster
jumping) as we still want to ignore cells with an empty evaluation in
those cases. The reason being that the user could be lost if, when
navigating with their keyboards, they end up with their selection on
empty cell.

As for #3214, the fix will need to be adapted to account for the
spreaded formulas.

closes #3573

Task: 3709340
Signed-off-by: Lucas Lefèvre (lul) <lul@odoo.com>
robodoo pushed a commit that referenced this pull request Feb 9, 2024
Similarly to the issue addressed in PR #3214, we want `loopSelection`
to consider seemingly empty cells when considering the expansion zone.

This revision splits the behaviour of the selection processor for
`loopSelection` and the other navigation features (like cluster
jumping) as we still want to ignore cells with an empty evaluation in
those cases. The reason being that the user could be lost if, when
navigating with their keyboards, they end up with their selection on
empty cell.

This PR is the adaptation of #3573 to support cells that contain the
result of a spreaded formula.

closes #3577

Task: 3709340
Signed-off-by: Lucas Lefèvre (lul) <lul@odoo.com>
@robodoo robodoo closed this Feb 9, 2024
fw-bot pushed a commit that referenced this pull request Feb 9, 2024
Similarly to the issue addressed in PR #3214, we want `loopSelection`
to consider seemingly empty cells when considering the expansion zone.

This revision splits the behaviour of the selection processor for
`loopSelection` and the other navigation features (like cluster
jumping) as we still want to ignore cells with an empty evaluation in
those cases. The reason being that the user could be lost if, when
navigating with their keyboards, they end up with their selection on
empty cell.

This PR is the adaptation of #3573 to support cells that contain the
result of a spreaded formula.

Task: 3709340
X-original-commit: 2e69e1b
robodoo pushed a commit that referenced this pull request Feb 9, 2024
Similarly to the issue addressed in PR #3214, we want `loopSelection`
to consider seemingly empty cells when considering the expansion zone.

This revision splits the behaviour of the selection processor for
`loopSelection` and the other navigation features (like cluster
jumping) as we still want to ignore cells with an empty evaluation in
those cases. The reason being that the user could be lost if, when
navigating with their keyboards, they end up with their selection on
empty cell.

This PR is the adaptation of #3573 to support cells that contain the
result of a spreaded formula.

closes #3664

Task: 3709340
X-original-commit: 2e69e1b
Signed-off-by: Lucas Lefèvre (lul) <lul@odoo.com>
Signed-off-by: Rémi Rahir (rar) <rar@odoo.com>
rrahir added a commit that referenced this pull request Feb 10, 2024
Similarly to the issue addressed in PR #3214, we want `loopSelection`
to consider seemingly empty cells when considering the expansion zone.

This revision splits the behaviour of the selection processor for
`loopSelection` and the other navigation features (like cluster
jumping) as we still want to ignore cells with an empty evaluation in
those cases. The reason being that the user could be lost if, when
navigating with their keyboards, they end up with their selection on
empty cell.

This PR is the adaptation of #3573 to support cells that contain the
result of a spreaded formula.

Task: 3709340
X-original-commit: 2e69e1b
robodoo pushed a commit that referenced this pull request Feb 10, 2024
Similarly to the issue addressed in PR #3214, we want `loopSelection`
to consider seemingly empty cells when considering the expansion zone.

This revision splits the behaviour of the selection processor for
`loopSelection` and the other navigation features (like cluster
jumping) as we still want to ignore cells with an empty evaluation in
those cases. The reason being that the user could be lost if, when
navigating with their keyboards, they end up with their selection on
empty cell.

This PR is the adaptation of #3573 to support cells that contain the
result of a spreaded formula.

closes #3665

Task: 3709340
X-original-commit: 2e69e1b
Signed-off-by: Lucas Lefèvre (lul) <lul@odoo.com>
Signed-off-by: Rémi Rahir (rar) <rar@odoo.com>
rrahir added a commit that referenced this pull request Feb 12, 2024
Similarly to the issue addressed in PR #3214, we want `loopSelection`
to consider seemingly empty cells when considering the expansion zone.

This revision splits the behaviour of the selection processor for
`loopSelection` and the other navigation features (like cluster
jumping) as we still want to ignore cells with an empty evaluation in
those cases. The reason being that the user could be lost if, when
navigating with their keyboards, they end up with their selection on
empty cell.

This PR is the adaptation of #3573 to support cells that contain the
result of a spreaded formula.

Task: 3709340
X-original-commit: 4ad2b93
robodoo pushed a commit that referenced this pull request Feb 12, 2024
Similarly to the issue addressed in PR #3214, we want `loopSelection`
to consider seemingly empty cells when considering the expansion zone.

This revision splits the behaviour of the selection processor for
`loopSelection` and the other navigation features (like cluster
jumping) as we still want to ignore cells with an empty evaluation in
those cases. The reason being that the user could be lost if, when
navigating with their keyboards, they end up with their selection on
empty cell.

This PR is the adaptation of #3573 to support cells that contain the
result of a spreaded formula.

closes #3668

Task: 3709340
X-original-commit: 4ad2b93
Signed-off-by: Lucas Lefèvre (lul) <lul@odoo.com>
Signed-off-by: Rémi Rahir (rar) <rar@odoo.com>
@fw-bot fw-bot deleted the saas-16.1-emptycell-not-cellvalue-rar branch February 23, 2024 14:47
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.

None yet

4 participants