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

Beet web queries are not parsed correctly #1045

Closed
oldtopman opened this issue Oct 28, 2014 · 2 comments
Closed

Beet web queries are not parsed correctly #1045

oldtopman opened this issue Oct 28, 2014 · 2 comments

Comments

@oldtopman
Copy link
Contributor

The search bar on the beet web interface functions as if the entire query was passed as a single argument to "beet list"

If you have a song titled "Word1 Word2 Word3", you can search for it like so:

beet ls Word1 Word3

Performing the same search on the web interface will not find any songs.

Word1 Word3

From my observations, the web plugin treats the entire query as a single argument, leading to the same (nonexistant) results that would be found of:

beet ls "Word1 Word3
@sampsyo
Copy link
Member

sampsyo commented Oct 28, 2014

Thanks! Just committed a client-side fix that splits on whitespace.

@oldtopman
Copy link
Contributor Author

Fix confirmed in 69b7d1f

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

No branches or pull requests

2 participants