Reader: Filter main feed based on sidebar selection

[mehmoodak]

Related to https://github.com/Automattic/loop/issues/236

Proposed Changes

• Extends the Recent menu item on sidebar with the list of subscribed posts which have also made it consistent with the new designs.
• Update the /following API calls to include the selected feed_id.

Why are these changes being made?

To enhance the filtering capabilities for feeds within the Reader's "stream" view.

Testing Instructions

• Navigate to /read
• Verify that filtering is working as expected
• Navigate to /read?flags=reader%2Frecent-feed-overhaul and select the stream view
• Verify that filtering is working as expected

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-126738

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-126738&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-126738&env=a8c-for-agencies

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~249 bytes added 📈 [gzipped])

name                             parsed_size           gzip_size
plugins                              +1408 B  (+0.0%)     +345 B  (+0.0%)
jetpack-cloud-plugin-management      +1408 B  (+0.1%)     +345 B  (+0.1%)
home                                 +1408 B  (+0.1%)     +345 B  (+0.1%)
reader                               +1026 B  (+0.1%)     +249 B  (+0.1%)
write-flow                            +411 B  (+0.1%)      +62 B  (+0.0%)
link-in-bio-tld-flow                  +411 B  (+0.0%)      +62 B  (+0.0%)
build-flow                            +411 B  (+0.1%)      +62 B  (+0.0%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Async-loaded Components (~105 bytes added 📈 [gzipped])

name                                                 parsed_size           gzip_size
async-load-design-blocks                                  +411 B  (+0.0%)      +62 B  (+0.0%)
async-load-calypso-components-web-preview-component       +411 B  (+0.1%)      +62 B  (+0.0%)
async-load-calypso-reader-sidebar                          -50 B  (-0.0%)      +43 B  (+0.2%)

React components that are loaded lazily, when a certain part of UI is displayed for the first time.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• notifications
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug loop-236/view-posts-of-the-selected-site-in-old-reader on your sandbox.

[holdercp]

Overall I think this looks good and we can roll forward with this.

I did stub out another approach that addresses some of the issues like the feeds overwriting each other if selections are made in quick succession. Here's the branch if you want to take a look. It's just prototype code but might be a direction we could take.

I fixed some TS errors that were related to the analytics calls, and I also suggest we remove the VSCode debug configs from this PR to keep this one tidy.

[holdercp]

This is working well!

• Feed is filtering by selection
• I can't trigger the "overriding feeds" issue 👍