Skip to content

[part 3] Port follower and current user datasource to miiverse-api#481

Open
mrjvs wants to merge 24 commits intodevfrom
feat/port-user-datasource
Open

[part 3] Port follower and current user datasource to miiverse-api#481
mrjvs wants to merge 24 commits intodevfrom
feat/port-user-datasource

Conversation

@mrjvs
Copy link
Copy Markdown
Contributor

@mrjvs mrjvs commented Apr 12, 2026

Changes:

  • Added follower/unfollow endpoints, also implemented into frontend codebase
  • Added follower/following listing endpoints, also implemented into frontend codebase
  • Added endpoint to list a users posts, also implemented into frontend codebase
  • Added endpoint to get the current user:
    • It does not error when banned, since it's used to get current account status as well
    • It's requested every frontend page and is the current auth state of the request
    • It does a few miscellaneous tasks: update mii name, set last_active, clear ban if date has passed
    • It's the replacement for getting the current user settings and current user content
  • Updated the guest guard, it now ignores bans as well. The user guard now checks it

Notes:

Resolves a part of #112

@mrjvs mrjvs changed the title Feat/port user datasource Port follower datasource to miiverse-api Apr 12, 2026
@mrjvs mrjvs changed the title Port follower datasource to miiverse-api Port follower and current user datasource to miiverse-api Apr 15, 2026
@mrjvs mrjvs changed the title Port follower and current user datasource to miiverse-api [part 3] Port follower and current user datasource to miiverse-api Apr 19, 2026
Base automatically changed from feat/port-post-feeds-datasource to dev April 26, 2026 09:58
@mrjvs mrjvs marked this pull request as ready for review April 26, 2026 10:21
@mrjvs mrjvs requested a review from ashquarky April 26, 2026 10:21
ashquarky
ashquarky previously approved these changes Apr 27, 2026
Copy link
Copy Markdown
Member

@ashquarky ashquarky left a comment

Choose a reason for hiding this comment

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

LGTM

@mrjvs
Copy link
Copy Markdown
Contributor Author

mrjvs commented Apr 27, 2026

Gonna wait for #494 before merging, otherwise we have another suite of tests to run before it

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.

2 participants