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

Feature: non-selector searchTag #28

Closed
TrySound opened this issue Oct 31, 2016 · 2 comments
Closed

Feature: non-selector searchTag #28

TrySound opened this issue Oct 31, 2016 · 2 comments

Comments

@TrySound
Copy link

@TrySound TrySound commented Oct 31, 2016

Would be great to pass instead of selector something like Element instance or even search string and then trigger search method. Maybe even call search with search string as an argument if searchTag is not specified. This will reduce dependency on DOM and selectors a bit.

@NeXTs NeXTs closed this in 8f1cd0a Oct 31, 2016
@NeXTs
Copy link
Owner

@NeXTs NeXTs commented Oct 31, 2016

Hi Bogdan,

I like this idea.
Try it this way

var jets = new Jets({
    contentTag: '#jetsContent',
    callSearchManually: true
})

jets.search('search phrase')

@TrySound
Copy link
Author

@TrySound TrySound commented Oct 31, 2016

Thanks a lot!

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

Successfully merging a pull request may close this issue.

None yet
2 participants