Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Order MemberGroup by name by default #3452

Merged
merged 2 commits into from
Nov 9, 2023
Merged

Order MemberGroup by name by default #3452

merged 2 commits into from
Nov 9, 2023

Conversation

ColonelPhantom
Copy link
Contributor

Closes #ISSUE.

Summary

@Scarletto wanted this for the effect on the events API. Ordering like this by default seems reasonable because i18n seems the only reason it wasn't done in the past and that's not a concern anymore.

How to test

  1. Go to an event in the API with many organisers
  2. Observe that organisers are sorted by name instead of PK or something else.
  3. See that this happens consistently.

Copy link
Member

@DeD1rk DeD1rk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The migration got outdated, but looks good!

This wasn't ideal for the old i18n-capable version of concrexit,
but we dropped that so the comment is outdated.

This does likely mean some redundant sorting is done, but that's not an
issue.
@DeD1rk DeD1rk added the feature Issues regarding a complete new feature label Nov 9, 2023
@DeD1rk DeD1rk merged commit ca77f66 into master Nov 9, 2023
10 checks passed
@DeD1rk DeD1rk deleted the organiser-order branch November 9, 2023 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Issues regarding a complete new feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants