MastoAPI transition: login/logout/register/verify credentials #439

Closed
opened 2019-03-11 21:37:35 +00:00 by hj · 1 comment
Owner
  • Should use entitiy_normalizer wherever possible for consistency.
  • Should not bring in regressions. (unless it's agreeable, see below)
  • Should not use extremely horrible hacks (up to reviewers to decide).
  • Should not rename everything nor bring tons of refactoring to avoid merge conflicts and ease the review and testing. (see below)
  • For every missing BE functionality there should be mention of it in pleroma#674, probably create a new task too.
  • Code from mastoapi-exploration branch could be backported/separated or used as a reference.

Right now, IIRC, credentials verification also register response as current user, which brings these problems:

  • i'm not sure MastoAPI does the same or you need to fetch your own profile separately
  • QvitterAPI also contains user's settings (see also pleroma#674, #437) which are absent in MastoAPI profile view so something needs to be done to be able to fetch your own settings and also raw (non-html) profile.
* Should use `entitiy_normalizer` wherever possible for consistency. * Should not bring in regressions. (unless it's agreeable, see below) * Should not use extremely horrible hacks (up to reviewers to decide). * Should not rename everything ~~nor bring tons of refactoring to avoid merge conflicts and ease the review and testing.~~ (see below) * For every missing BE functionality there should be mention of it in pleroma#674, probably create a new task too. * Code from mastoapi-exploration branch could be backported/separated or used as a reference. Right now, IIRC, credentials verification also register response as current user, which brings these problems: * i'm not sure MastoAPI does the same or you need to fetch your own profile separately * QvitterAPI also contains user's settings (see also pleroma#674, #437) which are absent in MastoAPI profile view so something needs to be done to be able to fetch your own settings and also raw (non-html) profile.
Member

I will work on this issue .

I will work on this issue .
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pleroma/pleroma-fe#439
No description provided.