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

Expand add panels flyout and increase default rows per page #30508

Merged
merged 49 commits into from
Feb 12, 2019

Conversation

flash1293
Copy link
Contributor

Summary

Builds on #30067 (has to be merged first).

Fixes #30356

This PR switches from a small flyout for the add panel to a medium one. To better use the space of the flyout, 15 instead of 10 items per page are shown as default (they fit on a 13inch non-retina screen).

The default items per page are configurable via initialPageSize to make SavedObjectFinder usable in other environments where space is small.

FYI @maryia-lapata

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

For maintainers

- [ ] This was checked for breaking API changes and was labeled appropriately
- [ ] This includes a feature addition or change that requires a release note and was labeled appropriately

timroes and others added 30 commits February 4, 2019 14:48
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app

@elasticmachine
Copy link
Contributor

💔 Build Failed

@cchaos
Copy link
Contributor

cchaos commented Feb 8, 2019

If we're messing with that add vis flyout, for the same reason I mentioned over here, we should consider using the EuiListGroup instead of the table to display the results.

It does mean doing more manual hook up with the search and pagination, but it's both a better DOM element and a better click area.

@flash1293
Copy link
Contributor Author

flash1293 commented Feb 8, 2019

@cchaos In #27985 we are thinking about to get rid of the tabs and use a unified list of saved objects instead. Would it make sense to move this requirement over to #27985 since we are touching the component there anyway?
Con: Lands in 7.1, not 7.0

Edit: The alternative would be to treat it as a separate issue @timroes created ( #30532 ) and do it ASAP for 7.0

@elasticmachine
Copy link
Contributor

💔 Build Failed

@flash1293
Copy link
Contributor Author

Jenkins, test this. Infra down

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Copy link
Contributor

@cchaos cchaos left a comment

Choose a reason for hiding this comment

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

Sound good, thanks!

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Dashboard Dashboard related features Team:Visualizations Visualization editors, elastic-charts and infrastructure v7.0.0 v7.2.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants