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

Fix "No results for {query}" message #742

Merged
merged 1 commit into from
Jun 14, 2018
Merged

Conversation

robertknight
Copy link
Member

Usage of vm.search.query in the <sidebar-content> template was
incorrect. vm.search is always set and query is a function that
returns a string, not a string.

Fixes #9

Usage of `vm.search.query` in the `<sidebar-content>` template was
incorrect. `vm.search` is always set and `query` is a function that
returns a string, not a string.

Fixes #9
@codecov
Copy link

codecov bot commented Jun 12, 2018

Codecov Report

Merging #742 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #742   +/-   ##
=======================================
  Coverage   91.07%   91.07%           
=======================================
  Files         139      139           
  Lines        5659     5659           
  Branches      970      970           
=======================================
  Hits         5154     5154           
  Misses        505      505

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f609e76...01915c0. Read the comment docs.

Copy link

@hmstepanek hmstepanek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@robertknight
Copy link
Member Author

Thanks Hannah 🙂

@robertknight robertknight merged commit 22de7ab into master Jun 14, 2018
@robertknight robertknight deleted the fix-empty-search-query branch June 14, 2018 07:23
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

Successfully merging this pull request may close these issues.

2 participants