GitLab

- both forms' validators tested

- check valid data
- comment out portion of clean_target

- one day I'll make up my mind on style

- add two links, make sure the old one is removed
- another one bites the dust :fiestaparrot:

- I don't have time to debug this atm, I just spent all day writing tests

- everything has at least one test now
- 504 lines later
- tests are of pretty ok quality, can be fairly sure models is tested to
it's extent now

- also remove some semicolons lol

- can they all increment?

- works, length, PK check

- that it accepts valid URLs and rejects long ones

- does it accept the date format?

- dhaynes -> evildhaynes

- test the booleans so that things don't break

- 1406: data too long

- find what the real exception is

- catch error thrown when tossing something too large into the DB

- test that it works, and that MYSQL will truncate fields

def main():
    """
        words about the function main()
    """

    print("Hello World!")

- this'll take a lot of work

- Plus __str__ now prints like registereduser does

- spacing issues fixed

- if text can be input
- or can be blank

- <Registered User: dhaynes - Approval Status: False>

- search function does the filtering
- triggered on keyup of each search field

(Closes #108)

- this will allow us to display form errors before calling the post method
- keep things nice and abstracted

- because I fixed it

(Closes #108)

Added logic which will (I think) prohibit links that lead to infinite loops or otherwise cause urllib.request.urlopen to throw an error.

Note this is a slight change from the original specs. Instead of prohibiting links which link to go at any stage of redirection (e.g. consider a go link to a bit.ly link to another go link to the final page), we prohibit links which loop infinitely (regardless of whether it's through go or not) AND links which have go at the first or last redirect stage.

The urllib.request.urlopen is potentially a costly operation. In particular, if the user enters a link that times out, I think it will hang for that entire period of time. Since we now have rate limiting and have always had to manually approve users in the first place, I think the risk of this inefficiency being exploited isn't prohibitively high.

Not final; I intend to fix up the comments, make the import look like it belongs there, and get feedback on how the error should be handled.

See last commit for more information about why
Tl;dr we are working on making it so that users can search both full and usernames
:zosman:

but it's kind of ugly I'll fix that later

- also remove obsolete setup file

- bunch of blanks for now