New orderby filters

[matti-lamppu]

🛠️ Changelog

• Add new order by filters to application, application events, and application event schedules endpoints

  • Applications
  • Events
  • Schedules

• Add new field filters to event reservation units for preferred order

🧪 Test plan

• Automated tests

🎫 Tickets

• TILA-2981

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
97.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[vergama]

Looks good except that I started wondering why are the sorters for application_event.name name_fi/en/sv rather than just name? (Thus already before this PR, though.)
In the test env for now this GQL does work but orderBy: "name_en" or orderBy: "name_sv", on the other hand, don't affect the sort order (but are accepted, nevertheless):

{ applicationEvents(applicationRound: 92, orderBy: "-name_fi") {
  edges { node {
    pk, name
  } }
} }

[matti-lamppu]

Looks good except that I started wondering why are the sorters for application_event.name name_fi/en/sv rather than just name? (Thus already before this PR, though.) In the test env for now this GQL does work but orderBy: "name_en" or orderBy: "name_sv", on the other hand, don't affect the sort order (but are accepted, nevertheless):

{ applicationEvents(applicationRound: 92, orderBy: "-name_fi") {
  edges { node {
    pk, name
  } }
} }

@vergama For translated fields, name is an alias for name_fi, since Finnish is our default language (this is hot django-modeltranslation works). So, using name will filter with the Finnish names, and can work that way. Still, I don't know why name_en and name_sv are accepted through the filter. I'm pretty sure it should give an error about non-existing filter. This could be a bug between django-modeltranslation and django-filter.