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

Feature add three six and nine months options backend #3226

Merged
merged 2 commits into from Jun 26, 2023
Merged

Feature add three six and nine months options backend #3226

merged 2 commits into from Jun 26, 2023

Conversation

c-andy-candies
Copy link
Contributor

I adapted the code from #3161 to add the sorting options for 3, 6 and 9 months which I think would be very cool to have, as someone pointed out here #3217

As the original PR I also am currently doing PRs for frontend and translations.

LemmyNet/lemmy-ui#1420

LemmyNet/lemmy-translations#69

This is my first contribution so please forgive me if I did something wrong.

@Nutomic
Copy link
Member

Nutomic commented Jun 21, 2023

Seems fine, but we shouldnt add any more after this. It will already result in a very long list.

Copy link
Member

@dessalines dessalines left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@dessalines dessalines enabled auto-merge (squash) June 26, 2023 18:38
@dessalines dessalines merged commit f5209ff into LemmyNet:main Jun 26, 2023
1 check passed
-- rename the old enum
alter type sort_type_enum rename to sort_type_enum__;
-- create the new enum
CREATE TYPE sort_type_enum AS ENUM ('Active', 'Hot', 'New', 'Old', 'TopDay', 'TopWeek', 'TopMonth', 'TopYear', 'TopAll', 'MostComments', 'NewComments');
Copy link
Contributor

Choose a reason for hiding this comment

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

this should include the TopHour, TopSixHour and TopTwelveHour enums

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You're right, I was not sure when I made the PR. Since now it has been merged, should I do another PR correcting it?

Copy link
Contributor

Choose a reason for hiding this comment

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

usually there's no take backsies with migrations, but I think in this case it's a down migration and is probably fine just opening a new PR with the hotfix of this file.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Opened a PR #3370

@L3v3L
Copy link
Contributor

L3v3L commented Jun 27, 2023

I think the migration needs to be timestamp after an already released migration or it wont run.
@dessalines

see: https://app.element.io/#/room/#lemmydev:matrix.org/$NZC0fV-P3hxQA4q8RTbtCXBQ8cMOEbX5g4UTRxbDG4U

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants