Option to select columns instead of hide columns #6858
Assignees
Labels
grid: column-hiding
🧰 feature-request
✅ status: resolved
Applies to issues that have pending PRs resolving them, or PRs that have already merged.
Comments
|
+1. Agree it would be nice to have this reversed (or at least configurable) |
|
There has been no recent activity and this issue has been marked inactive. |
github-actions
bot
added
the
status: inactive
|
There has been no recent activity and this issue has been marked inactive. |
github-actions
bot
added
the
status: inactive
DiyanDimitrov
removed
the
status: inactive
rkaraivanov
added
the
🛠️ status: in-development
rkaraivanov
added a commit
that referenced
this issue
Sep 28, 2020
Change the interaction for column hiding UI. Updated tests. Closes #6858
zdrawku
added
✅ status: resolved
zdrawku
added a commit
that referenced
this issue
Nov 6, 2020
* feat(grid-toolbar): Toolbar refactor Closes #8055 * feat(grid-toolbar): Hierarchical grid implementation Closes #8055 * refactor(grid-toolbar): Correctly grid context through templates in hierarchical grid * fix(grid): Deselect columns for hiding Change the interaction for column hiding UI. Updated tests. Closes #6858 * feat(grid): Emit when the grid is fully available in the DOM Closes #7924 * refactor(toolbar): Hierachical grid tweaks. Toolbar actions are rendered once the grid is 'fully' loaded in order to prevent expression changed after checked errors caused by updating the column collection. More unit tests updates. * chore(*): Dev demos updates * refactor(toolbar): Toolbar unit tests * refactor(tests): More unit tests * refactor(toolbar): Tests, api docs and tweaks * style(toolbar): provide styling for grid toolbar component * refactor(*): Unit tests * refactor(*): More unit tests * chore(styling): run stylelint --fix * refactor(toolbar): Even more unit tests * style(toolbar): update elevations, border & title width * update dropdowns border * refactor(toolbar): remove unnecessary selectors * refactor(toolbar): change elevation variable * docs(toolbar): remove unnecessary requires from sass docs * feat(grid-toolbar): Add basic migrations * feat(toolbar): Clean up migrations Migrate the toolbar based on the old input prop value * fix(migrations): File changes ordering * feat(toolbar): Template directive migration * fix(toolbar): Focus action comp input on open Remove filtering overlay keydown `catch'em all` handler. * feat(toolbar): Hierarchical grid migrations * fix(toolbar): Migration binding on empty directives * feat(toolbar): Migrate template context bindings * fix(toolbar): Backward compatible props * chore(toolbar): Unit tests tweaks * fix(toolbar): Toolbar width growing with pinned area * fix(toolbar): Expression changed error * fix(toolbar): Dropdown max height * fix(toolbar): Skip excel export dropdown * fix(toolbar): Choppy toggling of toolbar elements * refactor(toolbar): Address review comments Co-authored-by: Silvia Ivanova <[email protected]> Co-authored-by: Zdravko Kolev <[email protected]> Co-authored-by: Stamen Stoychev <[email protected]>
|
@GibletJr , the feature is to be available with the release of Ignite UI 11.0.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To allow a user to control what columns appear in the igx-grid, the columnHiding property must be set to true which presents the default IgxColumnHidingComponent. Our Engineering team is receiving multiple reports that requiring to check which columns to hide is the complete opposite of the Excel Style Filtering dialog which requires the user to check which data they want to see (attached screenshots).
I have reported the above confusing (and contradicting) UX in Support Ticket CAS-206171-T2N7N1.
We would like to see the option of reversing the current UX to select which columns to display; not hide. In the response to the above support ticket, a workaround was provided that does work but solely relies on overriding the default behavior by pulling elements by class names. This type of implementation has proven to be highly brittle and prone to breaking in subsequent releases as the IGX developers don't have an expectation that custom logic has been implemented using CSS class names.
The text was updated successfully, but these errors were encountered: