Skip to content

UI Component grid indicates a wrong number of selections when removin… #25253

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

Closed
wants to merge 6 commits into from
Closed

Conversation

ghost
Copy link

@ghost ghost commented Oct 23, 2019

wrong number of selections(selected records) in ui component grid #24348

Description (*)

After removing the full text search keyword the selected records and count mismatches. Which is fixed now.

Fixed Issues (if relevant)

  1. fixes UI Component grid indicates a wrong number of selections when removing keyword search #24348:UI Component grid indicates a wrong number of selections when removing keyword search

Manual testing scenarios (*)

  1. Setup some vanilla Magento
  2. Login to the backend
  3. Create 3 customers: 'One One', 'Two Two' and 'Three Three':
  4. In the 'Search by keyword' box, enter 'one' and search
  5. In the first column, choose the 'Select All' option
  6. Notice that one record is selected:
    I. Remove the 'one' keyword search by pressing the 'x' icon to the right of it.
    II. Notice that it now says that one record is selected, but visually all records have a checkmark:
  7. Select Actions => Delete
  8. Notice that it says it will remove 1 record:
  9. Press OK
  10. Notice that it now removed all records (3) instead of the 1 it claimed to delete before
  11. Press OK
  12. Notice that it now removed all records (3) instead of the 1 it claimed to delete before

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

@ghost ghost requested a review from DrewML as a code owner October 23, 2019 20:27
@m2-assistant
Copy link

m2-assistant bot commented Oct 23, 2019

Hi @prabhatrawat-webkul. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.3-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Guide documentation.

@sidolov sidolov changed the base branch from 2.3-develop to 2.4-develop December 5, 2019 17:17
@krzksz
Copy link
Contributor

krzksz commented Dec 8, 2019

Hey @prabhatrawat-webkul, please take a look at the failing tests.

@ghost ghost added Priority: P3 May be fixed according to the position in the backlog. Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Jun 12, 2020
@VladimirZaets
Copy link
Contributor

@magento run all tests

@ghost ghost removed Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. Priority: P3 May be fixed according to the position in the backlog. labels Aug 19, 2020
@sidolov sidolov added Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Severity: S1 Affects critical data or functionality and forces users to employ a workaround. labels Sep 2, 2020
@sidolov sidolov self-assigned this Sep 2, 2020
@sidolov
Copy link
Contributor

sidolov commented Sep 2, 2020

@magento run all tests

Copy link
Contributor

@sidolov sidolov left a comment

Choose a reason for hiding this comment

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

@prabhatrawat-webkul solution looks good to me! Could you please fix JS static test failures and cover changes with automated test? Thank you!

@engcom-Charlie engcom-Charlie self-assigned this Sep 7, 2020
@engcom-Charlie
Copy link
Contributor

HI, @prabhatrawat-webkul Could you please fix Static tests failures and cover changes with an automated test?
Thank you.

@gabrieldagama
Copy link
Contributor

Hi @prabhatrawat-webkul, thanks for your contribution. After looking at the issue and the possible solutions we've decided to proceed with this PR #29968 that aims to fix the same issue.

The approach that was chosen was to preserve the same behavior that we have with filters. So when a search tag is removed from filters the previous selection becomes invalid and it is dismissed. As result, we have the same behavior across multiple functionalities on the grid.

I will be closing this PR but feel free to reopen it anytime.

@m2-assistant
Copy link

m2-assistant bot commented Sep 15, 2020

Hi @prabhatrawat-webkul, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend Component: Ui Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: needs update Release Line: 2.4 Severity: S1 Affects critical data or functionality and forces users to employ a workaround. Squashtoberfest 2019
Projects
None yet
Development

Successfully merging this pull request may close these issues.

UI Component grid indicates a wrong number of selections when removing keyword search
7 participants