GitHub user tinkoff-dwh reopened a pull request:
https://github.com/apache/zeppelin/pull/2490
[Zeppelin-2718] Find and replace code in note
### What is this PR for?
Add feature for find and replace code in all paragraphs of note
### What type of PR is it?
[Feature]
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-2718
### How should this be tested?
Try to find and replace code in note (with help of search element)
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tinkoff-dwh/zeppelin ZEPPELIN-2718
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2490.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2490
----
commit f269b8aa79268d47c4baf1a5c2e3a4d681eb1354
Author: tinkoff-dwh <[email protected]>
Date: 2017-07-18T11:20:05Z
add find and replace feature
commit 9c662b4f7f2da68f2775f56f4e49f57fabfab14e
Author: tinkoff-dwh <[email protected]>
Date: 2017-07-19T13:49:52Z
add matches count
commit 8c163d82106a2a86f18aee4b16bdace5efc63d8a
Author: tinkoff-dwh <[email protected]>
Date: 2017-07-20T06:12:11Z
Merge remote-tracking branch 'upstream/master' into ZEPPELIN-2718
# Conflicts:
# zeppelin-web/src/app/notebook/notebook.controller.js
commit 7f524ae3e5b006ced5063e85d7b744e85c3188ca
Author: tinkoff-dwh <[email protected]>
Date: 2017-07-21T12:03:40Z
add e2e tests
commit a0cd3b1d64488f0493fc281c7d97ccaf81c57ccc
Author: tinkoff-dwh <[email protected]>
Date: 2017-07-24T08:05:15Z
add shortcut
commit 8808b7bc23a8fdfa4a145b078a9368e240d5c6ab
Author: tinkoff-dwh <[email protected]>
Date: 2017-07-24T08:27:45Z
fix borders
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
