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

Add sense as "console" kibana app #6682

Merged
merged 901 commits into from
Apr 4, 2016
Merged

Add sense as "console" kibana app #6682

merged 901 commits into from
Apr 4, 2016

Conversation

spalger
Copy link
Contributor

@spalger spalger commented Mar 28, 2016

This pr merges the history of the sense project and kibana by adding sense as a kibana application.

image

This pr is too big to review, but individual changes of meaningful complexity can be reviewed at these commits:

  • use resize checker: b59a241
  • implement navbar by copying dashboard: c8b5ab5
  • update style: 78d0039
  • remove sense docs for now, will readd from history: 802600e

spalger and others added 30 commits September 17, 2015 20:36
Preparing to serve the KB over the internet, we don't want to have to eval javascript
curl.parseCurl used to return requests objects. Now it's plain text
bootstrap shown event handling changed.

Closes #9
Added support for the field stats api
add autocomplete for _cat/nodeattrs
@spalger spalger added review and removed blocked labels Apr 1, 2016
@spalger spalger assigned w33ble and unassigned lukasolson Apr 1, 2016
@w33ble
Copy link
Contributor

w33ble commented Apr 1, 2016

Everything seems to be functional now. LGTM!

The first iteration of `kbnTopNav` prevented the need to define a `configTemplate` and the `menuItems` in separate locations, but moved the external API to a `kbnTopNav` object that was exposed on the scope where `kbnTopNav` was rendered. This meant that in order to programmatically control the `kbnTopNav` other directives needed to share a scope with it, or inherit from its scope. Additionally, since the `kbnTopNav` object is potentially not available when other directives boot, all access to this object needed to be wrapped in a call to `$timeout`.

In order to prevent this, but keep the nice API of `kbnTopNav`, this change breaks the controller and it's API out of `kbnTopNav` and exposes it via a Private module. Now, implementors can instantiate the `KbnTopNavController` themselves and pass it into the `<kbn-top-nav>` directive via the config attribute. This allows implementors to store the topNav API wherever makes sense in their implementation.

When the config attribute is not already an instance of the `KbnTopNavController` the directive will create an instance out of the passed value, which means that no existing implementations need to change at all.
@w33ble w33ble assigned lukasolson and unassigned w33ble Apr 4, 2016
@spalger spalger assigned spalger and unassigned lukasolson Apr 4, 2016
@spalger spalger merged commit 149b04c into master Apr 4, 2016
@epixa epixa deleted the feature/console branch April 5, 2016 01:14
@epixa
Copy link
Contributor

epixa commented Apr 5, 2016

Did this get a second review? I was suppose to review it according to the release doc, but I didn't realize it was ready to go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.