Skip to content

Conversation

dsevillamartin
Copy link
Member

@dsevillamartin dsevillamartin commented May 28, 2025

Very scuffed because it's my first dive into all the actual API changes.
This requires fof/extend flarum req changed -- its OAuthController seems to work mostly without changes though, but the extenders do need : void added

API routes are at:

Other:

  • Removed the custom LoginProviderStatus and just made that info show through the fields method of Resource (which replaces serializers)
  • Removed duplicate/unused CSS, renamed some divs
  • Haven't touched OAuth controller routing -- Discord at the very least remains working (including avatar on signup !)
  • Discovered that Flarum's common LabelValue is code split ([2.x] Make sure all common JS components, etc... are accessible flarum/framework#4219)

dsevillamartin and others added 7 commits May 28, 2025 10:42
Update dependencies to Flarum 2.0 compatible versions.
Flarum 2.0 completely changes the JSON:API implementation
Flarum 2.0 introduces a search driver implementation and moves gambits to the frontend.
I think it mostly works. The linked accounts endpoint is scuffed - currently an include on /users/{id} -- probably should do it like fof/reactions (https://github.com/FriendsOfFlarum/reactions/pull/89/files#diff-cae97e83649b4def60e51b7ea501d84bea77b47f838d4bcf0216d757038a3ae8). I used the Fields to replace LoginProviderStatus (a bit scuffed) and the complicated list logic.
@dsevillamartin
Copy link
Member Author

image

I've tested Discord, GitHub, and GitLab as OAuth providers, and they worked. Not sure about the rest - iirc Twitter is really hard to test due to verifications needed on the oauth app side.

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