QuerySearch | simple project to help | RecyclerView library

You can mock repositoryService and gitHubClient to test various scenarios.

You can provide a package-level setter for these fields. It is a great idea to annotate it with Guava VisibleForTesting annotation.

Then you need to set mocks before the actual test on the instance.

Pseudocode for mocking

You need to add this line:

It seems the reason your loadPage method is called twice due to your event listeners, but without sharing the code for those methods I cannot confirm that issue. The simplest way to fix your double call of the loadPage method would be this:

Well, you've got some mistakes in your snippet:

1. function oneCall() {... should be function oneCall(coord) { (the passed parameter when you call the function is not declared in the function itself)
2. coord is an object with lat and lon properties, not an array like you are using it, so you should have var ocLat = coord.lat and var ocLon = "&lon=" + coord.lon
3. The console.log you have inside the declaration of oneCall() won't work since it's after the return.

You could also use the data option of ajax() settings to querify your parameters for you by providing it an object, see: https://api.jquery.com/jquery.ajax/#jQuery-ajax-settings

You should make sure that the Elasticsearch mapping is properly created by Hibernate Search. By default, Hiberante Search will only create a mapping if it is missing.

If you launched your application once, then changed the mapping, and launched the application again, it is possible that the name field does not have the correct in Elasticsearch.

In development mode, try this:

By calling QueryParser.escape(queryString), you remove the meaning of operators such as :. So if the user enters name:test, you will end up looking for documents that contain name:test (literally), instead of looking for documents whose name field contains test.

Remove that escape and everything should work as you want.

By the way, you're essentially using Lucene to parse a query that will then be sent to Elasticsearch. An easier solution would be to send the query to Elasticsearch directly, especially if you do not need to prevent users from accessing some fields.