Add ability to search through applicants

[petschekr]

• Adds a bunch more information accessible via the GraphQL API such as:
  • Search result information (offset, count, total matching)
  • Login methods and admin status for users
  • Name of team
  • Label of form items (not just name)
  • Human formatted file size
• Allows you to search through applicants by name or email
• You can enable or disable searching with regular expressions
• Filter by confirmed / not confirmed in addition to accepted / no decision
  • (Filtering by confirmed / not confirmed only searches through accepted applicants)

Probably coming soon:tm:: displaying confirmation data in addition to the application data already present

Closes #183

[hackgbot]

Hey y'all! A deployment of this PR can be found here:
https://registration-search-applicants.pr.hack.gt

[ehsanmasdar]

Is SearchResult nullable?

[petschekr]

No it's not, I'll fix that

[ehsanmasdar]

What's the difference between accepted and not-confirmed? Where does not-confirmed apply to a user (since a single application branch can potentially have multiple confirmation branches)?

[petschekr]

Accepted includes all accepted applicants regardless of whether or not they have confirmed whereas not confirmed only includes accepted applicants who have not confirmed

[ehsanmasdar]

@illegalprime Is there a way to just specify "Get all info about the user"? That would clean up this query a lot

[ehsanmasdar]

Do we have to worry about escaping here since this is user supplied input?

[petschekr]

Escaping happens on line 54 right above this. Input is normally escaped unless the user ticks the Use Regex box in which case it is directly passed through. I don't see any security implications to doing that because the regular expressions only retrieve data and because this feature is already restricted to admins only.

[ehsanmasdar]

Might want to refactor this later if we ever want to add other login providers in a modular way