1. 15 Oct, 2021 2 commits
  2. 11 Oct, 2021 1 commit
  3. 03 Oct, 2021 5 commits
  4. 01 Oct, 2021 3 commits
  5. 30 Sep, 2021 3 commits
  6. 29 Sep, 2021 6 commits
    • Skia's avatar
      Merge branch 'genderMatmatroncheV2' into 'master' · 2cbe6fa1
      Skia authored
      Remove gender option of matmatronche & update gender settings
      Afin de se mettre à jour il est dorénavant possible de ne pas définir son genre sexué sur l'édit de son profil. D'ailleurs j'ai découvert que de base pour un profil random le sexe était défini sur "Homme" maintenant il est en "-------" !
      De plus afin que personnes n'utilisent l'outil matmatronche à des fins de site de rencontres en cherchant uniquement les "Homme" ou les "Femme" d'une promo etc... Le choix du sexe dans la recherche a été supprimé.
      C'est la première fois que je fais une modification en solo alors n'hésitez pas à me casser en deux et m'expliquer si j'ai fauté :D
      See merge request !264
    • Antoine Charmeau's avatar
    • Skia's avatar
      Merge branch 'poster' into 'master' · 6c45de34
      Skia authored
      [com]: add helper_text for resolution and format of poster
      See merge request !209
    • Théo Labetowiez's avatar
    • Skia's avatar
      Merge branch 'datetime-hell2' into 'master' · 007157e2
      Skia authored
      core: create TzAwareDateTimeField to replace forms.DateTimeField
      Follow up of !267. I read about Gitlab's slash and merge just after I did my own kind by resetting back to the original commit and creating one commit manually. Sublime merge helps but I still need more practice. :)
      What was the right way to group every commit under one?
      See merge request !270
    • tleb's avatar
  7. 28 Sep, 2021 1 commit
    • Skia's avatar
      Merge branch 'sexy-search' into 'master' · 782cd9a4
      Skia authored
      Sexy search
      The goal of this MR is to solve the search issue #96. Let's assume we have a user with firstname `Jean-François`, lastname `Du Pont` and nickname `Ai'gnan`. Here is a list of search that did not include him previously but now includes him (was and still is case-insensitive):
      * `jean françois` (missing -) ;
      * `jean-francois` (missing ç) ;
      * `jean francois` (both) ;
      * `dupont` (space) ;
      * `françois` (not the start of his name) ;
      * `aignan` (missing ').
      You get it, there are a lot of mistakes that humans can do. It also sorts results by `User.last_update` to avoid putting old accounts at the top of common requests (such as firstname-only or lastname-only requests).
      ### How it works
      For those who don't know, the search is handled by Xapian (the search backend) through the haystack library which provides a Django-friendly interface to multiple search backends. Xapian maintains kind of a duplicate of the database (only for models against which we want to search something) which is optimised for search operations. Its "models" are called "indexes" (see `core.search_indexes.UserIndex` for the user model).
      Every time a user is created or modified, it is indexed (through a signal handler) so that Xapian knows about it. For the user search, what is indexed is the string outputted by the `core/templates/search/indexes/core/user_auto.txt` template. For our example from above, it looks like this:
      jean francois
      du pont
      As you can see, unicode is removed. There also are kind-of duplicates with different spacing as we are using an autocomplete algorithm: it searches from the beginning of words.
      The one I am not sure about is the last one. Its goal is to allow searching without putting a space between the firstname and lastname. Is this useful?
      The prod will have to do a `./manage.py update_index`, not sure it does it in the upgrade script.
      See merge request !269
  8. 27 Sep, 2021 9 commits
  9. 26 Sep, 2021 5 commits
  10. 21 Jul, 2021 1 commit
  11. 23 Apr, 2021 2 commits
  12. 31 Aug, 2020 1 commit
  13. 30 Aug, 2020 1 commit