Apply labelers and handle language for PWI home #5816
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Noticed two things were happening:
getFeed
requestsgetFeed
requestsI don't think we've ever noticed the first, and the second I broke when I untangled
appLanguage
fromcontentLanguages
in #5384. We used to setcontentLanguages
to match theappLanguage
when that field was changed. I understood this to be a UX decision without realizing that it was load bearing for the PWI experience. Since post recordlang
field doesn't support regional codes either, I don't think this has ever worked as intended for "app" languages with region codes.This PR borrows the labeler logic from our base
Agent
class, and pulls the language value we pass togetFeed
from theappLanguage
setting, stripping out a region code if it exists.Testing
atproto-accept-labelers
is applied for PWI feed fetchesatproto-content-labelers
to see which are applied