MastoAPI transition: user search #438

Closed
opened 2019-03-11 21:32:05 +00:00 by hj · 0 comments
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.
  • 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.

Soft-depends on #1925, can be done in parallel but expect glitches without it. No known issues, sorry.

* 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. * 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. Soft-depends on #1925, can be done in parallel but expect glitches without it. No known issues, sorry.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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#438
No description provided.