* Restructure dashboard files and folders
* Try to stay DRY
avoid duplicate ‘dashboard’ naming when unnecessary
* rename index => dashboard and add an index.js with imports
rename style
* un-dig
* [ui/tilemapSettings] verify that the manifest has a service information
* [ui/tilemapSettings] stop reading query_parameters from manifest
* [ui/tilemapSettings] allow the manifest to define subdomains
* [ui/tilemap] add error handling for foreign error types
* [ui/tilemapSettings] update manifest in tests to match new format
* - Remove need for passing state to dashboard_panel directive.
get rid of parentUiState
* Address code review comments
* Only do savedSearch specific init stuff for searches
* Throw Error object, not string
* Remove new patterns from this PR
Removing the new patterns from this PR to preserve consistency.
Eleasticsearch notfies usage of deprecated feature via a special http header. This commit exposes the value of this header in the output pane. To so a special type of comment is added - a warning comment, marked by a `#!` prefix.
* Introduce custom modal confirmation dialogs
* address code review comments
and implement new angular style suggestions from Joe
* refactor
no point making vanilla code that's really only going to work with angular i guess...
also broke apart the confirm modal from the injector, and made safeConfirm just use the confirm modal
* Clean up from merge
- Move safe_confirm into modals folder
- make data-test-subj camelCase.
- get rid of $timeout call, doesn’t seem necessary anymore, now that
window.confirm is not being used.
* Fix tests
* Use ui-framework styles
* Address latest round of comments and remove adoption of new patterns.
* Improve error message. Use sinon in tests.
* Focus on the confirm button by default
* Indent message
* Override Bootstrap link styles in Button component. Give kuiStaticInput a transparent background.
* Fix incorrect markup in MicroButton examples.
* Give Bar component a min height of 30px so it has a consistent height even when it has shorter children.
* Remove kuiSubHeader class. Migrate Saved Objects to use Bar component instead.
* Make sure new dashboards get a title
Fix misleading “ready to get started” message for empty dashboard.
* Revert dashboard is empty name
get rid of tab reference in string
* be more playful!
- Make table-layout use the default, instead of fixed.
- Fix flexbox bug with ToolBar.
- Update ui_framework task to serve on port 8020.
- Add babel-core/polyfill to UI Framework docs site.
* - Remove angularization of PersistedState.
- Provide the angularized version with PersistedStateProvider.
- Use named exports
- Es6-ify PersistedState class
This pushes forward the first bullet point of #9686
* Address code review comments
- Use single point of entry
- Use injector instead of private
- Use a new class (‘AngularizedPersistedState’) name instead of an
arrow function
* Remove extra import line
* switch to query_string query
and only append trailing * when the query is a simple word
* swallow 400 errors from query_string query
attempt to mimic simple_query_string...
> Unlike the regular query_string query, the simple_query_string query will never throw an exception, and discards invalid parts of the query
> https://www.elastic.co/guide/en/elasticsearch/reference/5.1/query-dsl-simple-query-string-query.html
* simplify the regexp
no grouping required, and matching 1 or more is fine, as this condition isn't met when the searchString is empty
* Add Bar component.
* Create modifier for a ToolBar with just Search.
* Add Select component.
* Fix focus state of ToolBarSearch.
* Add Select to ToolBar.
* Rename onReverseBackground mixin to onStandoutBackground.
When the UglifyJsPlugin is used for production, it's setting the minimize property for the loaders in the pipeline. This was causing the css-loader to call cssnano which was itself then calling autoprefixer.
We were explicitly calling autoprefixer via the postcss-loader for all style loaders that utilized a preprocessor and specifying the list of supported browsers, specifically to set the prefixes for PhantomJS. When the autoprefixer was run as part of the css-loader, the list of browsers wasn't present and this was causing the prefixes that we added to be removed.
This removes the implicit use of autoprefixer from the css-loader and instead explicitly uses the postcss-loader for all style loaders, passing in the proper configuration.
* Update managing-fields.asciidoc
* Remove references to Groovy
* Add information about Painless
* Link to blog for additional examples
* Update managing-fields.asciidoc
Make editorial changes per @debadair's feedback.
* [tribe] Init docs
* [docs] Init es client section
* [docs] Link to client api, move client library docs to core development section
* [docs] Add tribe server settings
* [tribe] Link to elasticsearch tribe docs
* [tribe] Document which nodes server configuration points towards
* [docs] Add index link to elasticsearch clients section
* Add boolean property to show blank rows or not.
The property defaults to true to preserve backwards compatibility.
* Don't show blank rows in list of indexed fields on index-pattern page
* Don't show blank rows in list of scripted fields on index-pattern page
* Adding unit test for showBlankRowsAtBottom property
* Shortening variable name
* Simplifying logic
* Missed a spot (source filters)
* Using template literal syntax instead of string concatenation
* Removing horizontal rule as it doesn't appear to break visual flow IMO
Formats other than "Color" on this page (e.g. "Url", "Bytes", etc.) seem to use the horizontal rule to separate their editor fields from samples. Since the Color editor does not seem to have samples, the horizontal rule seems out-of-place for this particular format.
* Bringing the "x" button vertically in line with the editor labels
* Adjusting some vertical margins to improve (IMO) spacing
* Removing unnecessary rule
* Close timepicker when a filter/interval is selected
* Copy absolute variables before sending
* Use & instead of = for directive binding
* Fix timepicker tests
* Fix timepicker tests and remove tests that no longer apply
Remove libsass as a dependency
libsass is platform specific, therefore we can not ship it as a dependency. Instead, we will commit the compiled CSS for the UI Framework to the repository. This is updated when running `npm run uiFramework:start` which also starts the docs site.
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
In `tutorial-define.text.asciidoc`, it is stated that the typical index name contains the date as `MM-DD-YYYY`, and then proceeds to give an example of how a log index from May, 2015 would look like: `logstash-2015.05*`, which doesn't match the typical pattern for dates stated above.
This PR changes the date pattern, as to me `YYYY.MM.DD` is more accurate on a world-wide scale.
The default panel size is almost always too small for anyone’s needs.
Using half the width per vis seems to work better, along with making
slightly taller.
* [ui/vis_maps/tests] use $injector to avoid awkward naming
* [ui/vis_maps/tests] avoid boolean assertions for better error messages
* [ui/vis_maps/tests] verify addQueryParams behavior over time
* [ui/vis_maps/tests] stub tilemapsConfig rather than monkey-patching it
* [ui/vis_maps] remove async/await usage because angular
* [ui/vis_maps/tests] add failing test
* [ui/url] add modifyUrl() helper
* [ui/vis_maps] use modifyUrl() helper to extend query string
* Incorporate refactors to prep for view-edit mode
* code review comments
- Get rid of top nav config factory function refactor as it makes the
parameters less clear.
- Remove the watch on topNavMenu since it isn’t necessary for this PR.
Will bring a better variation back in the view/edit mode PR.
Note that these changes look somewhat pointless in and of themselves,
but the refactor will be useful for the view/edit mode when the top nav
configuration will change based on the dashboard mode, and then the
refactored functions, which are all only being used one currently, will
be called multiple times.
