Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Social: Base PR: Unified connections management #40679

Open
wants to merge 25 commits into
base: trunk
Choose a base branch
from

Conversation

manzoorwanijk
Copy link
Member

@manzoorwanijk manzoorwanijk commented Dec 19, 2024

Proposed changes:

Other information:

  • Have you written new tests for your changes, if applicable?
  • Have you checked the E2E test CI results, and verified that your changes do not break them?
  • Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Testing instructions:

@manzoorwanijk manzoorwanijk force-pushed the social/unified-connections-management branch from 2d2dbd8 to 56c0fbc Compare December 19, 2024 08:26
Copy link
Contributor

github-actions bot commented Dec 19, 2024

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

  • To test on WoA, go to the Plugins menu on a WordPress.com Simple site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin, and enable the social/unified-connections-management branch.

    • For jetpack-mu-wpcom changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file.
  • To test on Simple, run the following command on your sandbox:

    bin/jetpack-downloader test jetpack social/unified-connections-management
    
    bin/jetpack-downloader test jetpack-mu-wpcom-plugin social/unified-connections-management
    

Interested in more tips and information?

  • In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
  • Read more about our development workflow here: PCYsg-eg0-p2
  • Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

Copy link
Contributor

github-actions bot commented Dec 19, 2024

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  • ✅ Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖


The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.


Follow this PR Review Process:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Choose a review path based on your changes:
    • A. Team Review: add the "[Status] Needs Team Review" label
      • For most changes, including minor cross-team impacts.
      • Example: Updating a team-specific component or a small change to a shared library.
    • B. Crew Review: add the "[Status] Needs Review" label
      • For significant changes to core functionality.
      • Example: Major updates to a shared library or complex features.
    • C. Both: Start with Team, then request Crew
      • For complex changes or when you need extra confidence.
      • Example: Refactor affecting multiple systems.
  3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

@manzoorwanijk manzoorwanijk reopened this Dec 19, 2024
@manzoorwanijk manzoorwanijk added the [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it label Dec 19, 2024
@manzoorwanijk manzoorwanijk self-assigned this Dec 19, 2024
@manzoorwanijk manzoorwanijk force-pushed the social/unified-connections-management branch 2 times, most recently from a749a20 to 9af33a7 Compare December 26, 2024 05:12
* Create connections class for caching

* Update script data to use connections from the REST endpoint

* changelog

* Restore deprecated connection fields for time being

* Disable caching for now

* Fix display_name for Mastodon

* Remove the unused caching logic
@manzoorwanijk manzoorwanijk force-pushed the social/unified-connections-management branch from 9af33a7 to 4af0cc4 Compare January 7, 2025 05:01
* Social: Use connections REST endpoint for initial state (#40677)

* Create connections class for caching

* Update script data to use connections from the REST endpoint

* changelog

* Restore deprecated connection fields for time being

* Disable caching for now

* Fix display_name for Mastodon

* Remove the unused caching logic

* Update connect-form.tsx

* Create connections class for caching

* Update types for connection object

* Update connection actions to reflect new types

* Mark 'id' as deprecated

* Add changelog

* Deprecated fields should be optional

* Fix TS error

* Update unit tests

* Replace/remove deprecated props usage

* Remove unused code

* Fix connection selectors

* Fix unit tests

* Reduce the number of changes

* Fix type

* Oops! It should be negation

* Restore class-connections.php
* Allow requests as blog in base controller

* Add filters for connections controller

* Add changelog

* Update baseline.php

* Rename the 'include' param to 'scope' for clarity

* Return shared connections by default

* Remove scope parameter in favour of request context

* Only pass test_connections to WPCOM

* Update baseline.php
* Update connections class to implement caching

* Add get_all_for_user method

* Pass cached connections to initial state

* Invalidate cache on XMLRPC request

* Add changelog

* Remove eager loading of connections following cache invalidation

* Improve clear caching logic to handle race condition
* Pass the connected users WPCOM data to the UI

* Augment wpcom for user object

* Create canUserManageConnection selector

* Replace can_disconnect with the new selector

* Fix unit tests

* Add changelog

* Fix user data for WPCOM sites

* Fix unit tests

* Add changelog
manzoorwanijk and others added 2 commits January 10, 2025 23:11
* Add "must_reauth" to status in REST schema

* Restore the UI changes to consider must_reauth status

* Add changelog

* Don't disable connections with must_reauth status

must_reauth means that the connection will break soon, but it still
works. We'll display an appropriate notice.

---------

Co-authored-by: Paul Bunkham <[email protected]>
…0982)

* Create Proxy_Requests class for re-usability

* Move is_wpcom utility to Publicize_Utils class

* Move connections specific logic from REST controller to connections class

* Add changelog

* Update baseline.php

* Move publicize permissions check to its own method
manzoorwanijk and others added 13 commits January 13, 2025 18:51
…reen (#40997)

* Social | Fix connected accounts not marked as such on confirmation screen

* Add a comment
…_id` (#41025)

* Social | Update connections schema to change user_id to wpcom_user_id

* Fix wpcom_user_id for post connections field

* Add changelog
* WIP

* Pass the connection ID in the URL

* Pass connection_id for delete proxy request

* Allow overriding $request_options

* Clean up debugging

* Add changelog

* Add changelog for js changes

* Fix static analysis issues

* Remove unused code

* Update baseline.php

---------

Co-authored-by: Paul Bunkham <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant