7 kyu

Google Dorking - Validating Queries

223 of 384chr3st5an
Description
Loading description...
Regular Expressions
View
AllIssues6QuestionsSuggestionsShow Resolved
  • Please sign in or sign up to leave a comment.
  • pavloslav Avatar

    The description claims that

    intext:"google dorking" site:codewars.com

    gives exactly 1 result, but it gives 2 to me and will be more because some pages have "SIMILAR KATA:" section.

    Not a great issue, but still...

    • khanhtranngoccva Avatar

      I don't think it's a general issue, Pavloslav! It'd fit into the suggestion category though in my opinion. šŸ˜Š

      By the way, 1 result was the expected lookup count, most probably because the kata was in beta (I approved this morning after fixing issues). Once approved, the kata is more likely to be put into the "similar kata" as you said.

      Issue marked resolved by khanhtranngoccva 3 years ago
  • khanhtranngoccva Avatar

    Description for which filters are valid is missing (as Voile mentioned) and has not been fixed in JavaScript. At least you should provide a preloaded array of allowed filters.

  • Voile Avatar

    The grammar of a filter (<filter-name>:<value>) has not been defined in the description. What exactly are the filter names of allintext:kitten dogs animals after:2020, or breaking new site:amazingnew.org? Why should we consider site as filter name and not breaking new site?

    • chr3st5an Avatar

      Hello,

      I am sorry if it is not clear enough but filters are always followed by a :, e.g. allintext:blah -> filter: allintext, the value of the filter is hence on the right. Multiple filters are seperated by a space. Everything else belongs to the search query itself.

      allintext:kitten dogs animals after:2020 -> filters: allintext, after

      Issue marked resolved by chr3st5an 3 years ago
  • Blind4Basics Avatar

    Hi again,

    Issue part:

    • The initial solution should import FILTERS explicitly from preloaded
    • it is very unlikely, yes, but the invalid_filters might end up containing a valid filter, one day (on thousands of solvers doing a lot of attempts, you'll statistically see one or two potentially popping up) => the random invalid filters should be filtered to ensure it will never happen

    Suggestion part:

    • instead of building a random string, splitting, shuflling and then joining again, a list should be built, shffled, then joined
    • rather than picking in some random invalid queries, you could generate fresh ones each time you need it. Same for the values of the valid filters.

    Cheers

  • Amish Mathais Avatar

    I'm so dumb that I did not even see that I could access valid filters using FILTERS.

    Great kata though!

  • Blind4Basics Avatar

    Hi,

    This kind of situation is covered neither by the description nor by the fixed tests and showing up in the random tests: intitle:XNELqBGbuGS:lhM. Your solution expects False for this.... Why!??

    Cheers

  • rowcased Avatar

    I have created yet another sometimes pass solution.