Uh oh!
There was an error while loading. Please reload this page.
ZEPPELIN-866] Hotfix - does not working search box on navbar. - #911
ZEPPELIN-866] Hotfix - does not working search box on navbar.#911cloverhearts wants to merge 5 commits into
Conversation
| $scope.search = function() { | ||
| $location.url(/search/ + $scope.searchTerm); | ||
| $scope.search = function(searchTerm) { | ||
| console.log('search term ', searchTerm); |
There was a problem hiding this comment.
Can you remove console.log from here.
prabhjyotsingh
commented
May 23, 2016
If we use |
cloverhearts
commented
May 23, 2016
@prabhjyotsingh |
prabhjyotsingh
commented
May 23, 2016
Or that is also broken for |
cloverhearts
commented
May 23, 2016
@prabhjyotsingh Okay, i will look to this issue. |
@prabhjyotsingh |
cloverhearts
commented
May 24, 2016
@prabhjyotsingh |
bzz
commented
May 24, 2016
Thanks for hotfix, but do we know why it stopped working in the first place? \cc @felizbear for review as well |
astroshim
commented
May 24, 2016
I tesed and working well. but it seems need a "initial statement". |
| <form role="search" | ||
| style="width: 300px; display: inline-block; margin: 0 10px" | ||
| ng-submit="search()"> | ||
| ng-submit="search(searchTerm)"> |
There was a problem hiding this comment.
i definitely like passing the argument to search instead of taking it from the $scope 👍
@astroshim Thank you for feed back. |
@cloverhearts I agree with @astroshim. I think he was saying that when the result is nothing, Zeppelin needs to show some statement like "We couldn’t find any notebook matching 'something_you_typed' " |
astroshim
commented
May 24, 2016
Thanks for the detail explanation AhyoungRyu. |
cloverhearts
commented
May 24, 2016
Thank you for explaining, @astroshim@AhyoungRyu |
AhyoungRyu
commented
May 24, 2016
@cloverhearts Yeah you're right. LGTM 👍 |
prabhjyotsingh
commented
May 24, 2016
I think this sounds good, have created a jira for the same https://issues.apache.org/jira/browse/ZEPPELIN-869. LGTM. |
@prabhjyotsingh could you please wait, as there was an issue raised, but not addressed yet?
It would be really cool, if we could know the answer, as I think it might help us avoiding such bugs further down the road. @cloverhearts could you please share, if you have already done some investigation before? |
prabhjyotsingh
commented
May 24, 2016
Surething. |
cloverhearts
commented
May 25, 2016
@bzz I think we need to recover the ability to hotfix first. |
bzz
commented
May 25, 2016
@cloverhearts fix looks great to me. Pity that we can not identify the source of the bug though. Let's merge as a hotfix! |
prabhjyotsingh
commented
May 25, 2016
Sure, I'll merge this. |
### What is this PR for? When you type in the search box and start the search, The result is not exposed. Previously, it was working well. ### What type of PR is it? Hot Fix ### Todos * [x] - fixed bug on navbar.html and controller ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-866 ### How should this be tested? try to search action on navbar. ### Screenshots (if appropriate) #### before <img width="1280" alt="test02" src="https://cloud.githubusercontent.com/assets/10525473/15469402/10713c64-2125-11e6-909d-cb375e7c31a4.png"> #### after <img width="1280" alt="test01" src="https://cloud.githubusercontent.com/assets/10525473/15469411/1a6e0b0c-2125-11e6-9ade-e4147e7143d8.png"> ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? no Author: CloverHearts <cloverheartsdev@gmail.com> Closesapache#911 from cloverhearts/fixed/searchbar and squashes the following commits: bca027b [CloverHearts] remove whitespace c592422 [CloverHearts] add space in navbar.controller.js 433139a [CloverHearts] removed event locationChangeSuccess on pr ( does not working search bar) bac1254 [CloverHearts] removed console.log (pr does not working search box) 4d06560 [CloverHearts] Hotfix - dose not working search box on navbar.
What is this PR for?
When you type in the search box and start the search,
The result is not exposed.
Previously, it was working well.
What type of PR is it?
Hot Fix
Todos
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-866
How should this be tested?
try to search action on navbar.
Screenshots (if appropriate)
before

#### after
### Questions: - Does the licenses files need update? no - Is there breaking changes for older versions? no - Does this needs documentation? no