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 Request: Better clarity on error messages #7

Open
clening opened this issue Jun 26, 2022 · 1 comment
Open

Feature Request: Better clarity on error messages #7

clening opened this issue Jun 26, 2022 · 1 comment

Comments

@clening
Copy link

clening commented Jun 26, 2022

I've recently created a Goggle and notice that the error messages displayed are often unhelpful to a user (especially to someone who isn't a software engineer. Case in point:

Line 70: Invalid character in site value

Here's my line 70: $boost=10,$site=^ca.gov

Line 77: There was an error processing your Goggle

$boost=10,$site=lis.virginia.gov

It would be helpful if errors were a bit more verbose - for example, what character is making Goggles sad? For Line 77, is there an error code from the website, or is this a formatting issue?

Suggestion Please consider adding more verbose error handling.

@remusao
Copy link
Collaborator

remusao commented Jun 26, 2022

Hi @clening,

Thanks for reaching out. We will definitely consider making the error messages more clear in the future as in this case I agree that they are not very useful.

I think your instruction $boost=10,$site=^ca.gov could be written as $boost=10,site=ca.gov. The $ character only needs to be specified once to signify the start of an option list (coma-separate). What comes before $ is the (optional) pattern that would need to match the URL of the result (e.g. /some/pattern$boost=10).

The second instruction could be written as $boost=10,site=lis.virginia.gov (same reason as above).

Would you be able to share the URL where your Goggle is hosted so that I can have a closer look?

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