🔥 Feature: add queryBool parser

[dozheiny]

Hi!
Before this PR, I wrote this feature for integer variables #2306 And float variables #2328.
Now I wrote this feature for boolean variables,
With this parser, you can easily extract bool values from URL queries. You can pass the desired key and the URL string to the parser, which will return the boolean value associated with that key. This eliminates manual string parsing and makes retrieving the values you need easier.

[li-jin-gou]

Next time PR can be merged, as the functions are similar

[dozheiny]

Next time PR can be merged, as the functions are similar

Yes, you are right. I will resolve conflict files.

[dozheiny]

I don't know why PR closed; I think because pulled resolved conflicts.

[gaby]

LGTM

[crdx]

This may not be the right place for this but I didn't want to clog up the issues list with a simple question.

What's the reason for QueryBool() returning true for a non-existent key? Since the default value of a bool in Go is false, I would have expected it to be false here too.

[dozheiny]

Most frameworks (in other languages, not just in Go) will calculate the boolean value true actual if it is a string.
That means If the convert fails, it returns true (with an error).

[crdx]

Yes, in the string case true is returned and that's expected. I'm talking about in the case of the parameter not existing at all. The documentation for QueryBool has a warning saying this, as well:

Please note if that parameter is not in the request, true will be returned.

Compare to QueryFloat:

Please note if that parameter is not in the request, zero will be returned.

0 is the zero value for a float, so that's what is returned. For a bool false is the zero value, so shouldn't it be what's returned? To me it makes as much sense as QueryFloat returning an arbitrary value like 123 if the key doesn't exist.

I can't think of a situation where you want to query a non-existent key and get true back if it doesn't exist... what am I missing here?

[dozheiny]

No. I think you are right.

[ReneWerner87]

@dozheiny can you provide a PR with a change (function, docs)

[dozheiny]

Sure, I'll do it.