Fix search failing test

[JuanVqz]

This PR is just for fixing the latest merge that introduces a failing
test.

When initializing a new Search model it has some default values,
especially the results_count one.
https://github.com/JuanVqz/lobsters/blob/5338e5a4b335b94337636a59b7bbc83529dfce81/app/models/search.rb#L42

When doing Search.new({}, nil) in the ignore_searx method
https://github.com/JuanVqz/lobsters/blob/5338e5a4b335b94337636a59b7bbc83529dfce81/app/controllers/search_controller.rb#L30

It takes the -1 value by default which in this if/else statement

https://github.com/JuanVqz/lobsters/blob/5338e5a4b335b94337636a59b7bbc83529dfce81/app/views/search/index.html.erb#L40

is rendering this else block

https://github.com/JuanVqz/lobsters/blob/5338e5a4b335b94337636a59b7bbc83529dfce81/app/views/search/index.html.erb#L157-L167

and that doesn't render the 0 results but it renders the Search hints:

if that is the required behaviour then this PR is solving it.
otherwise, let me know and I'll arrange it as desired.

[pushcx]

Thanks for fixing this. I guess I’d prefer to return 0 results without an error message. This isn’t currently possible with the Search model. Do you see an unintrusive way to make that possible?

[JuanVqz]

Thanks for fixing this. I guess I’d prefer to return 0 results without an error message. This isn’t currently possible with the Search model. Do you see an unintrusive way to make that possible?

@pushcx I updated it, let me know what you think about it.

Another option could be to redirect to another page instead of rendering index

[pushcx]

This works nicely, thank you.