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

Toolbar refactor #8158

Merged
merged 82 commits into from
Nov 6, 2020
Merged

Toolbar refactor #8158

merged 82 commits into from
Nov 6, 2020

Conversation

rkaraivanov
Copy link
Member

@rkaraivanov rkaraivanov commented Sep 16, 2020

Closes #8055
Closes #7924
Closes #6858

Additional information (check all that apply):

  • Bug fix
  • New functionality
  • Documentation
  • Demos
  • CI/CD

Checklist:

  • All relevant tags have been applied to this PR
  • This PR includes unit tests covering all the new code (test guidelines)
  • This PR includes API docs for newly added methods/properties (api docs guidelines)
  • This PR includes feature/README.MD updates for the feature docs
  • This PR includes general feature table updates in the root README.MD
  • This PR includes CHANGELOG.MD updates for newly added functionality
  • This PR contains breaking changes
  • This PR includes ng update migrations for the breaking changes (migrations guidelines)
  • This PR includes behavioral changes and the feature specification has been updated with them

@rkaraivanov rkaraivanov changed the title Rkaraivanov/toolbar refactor Toolbar refactor Sep 16, 2020
through templates in hierarchical grid
Change the interaction for column hiding UI.
Updated tests.

Closes #6858
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.
@ddincheva
Copy link
Contributor

All the issues described in my previous comment are fixed except that in the 4th checkbox. But a new issue is introduced. When open the "Export" button an error is thrown:
excellError

};

const moveTemplateIfAny = (grid: Element) => {
const ngTemplates = findElementNodes([grid], ['ng-template']);
Copy link
Member

Choose a reason for hiding this comment

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

It's possible for the template to be using the short syntax (<div *igxToolbarCustomContent...) that won't be found searching for just ng-template. As far as I see most of our code examples are covered, but to be thorough, try to capture both versions if it doesn't get too messy.

@Aleksandyr Aleksandyr added ✅ status: verified Applies to PRs that have passed manual verification and removed 💥 status: in-test PRs currently being tested labels Nov 6, 2020
ChronosSF
ChronosSF previously approved these changes Nov 6, 2020
@zdrawku zdrawku merged commit c267b3c into master Nov 6, 2020
@zdrawku zdrawku deleted the rkaraivanov/toolbar-refactor branch November 6, 2020 13:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
grid: toolbar squash-merge Merge PR with "Squash and Merge" option version: 11.0.x ✅ status: verified Applies to PRs that have passed manual verification
Projects
None yet
8 participants