-
Notifications
You must be signed in to change notification settings - Fork 1
Add Disconnect Functionality for Jobber Integration #28
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
Conversation
|
@TylerB24890 Just a heads up: this PR introduces a REST endpoint at jobber-wp/includes/classes/Disconnect.php Lines 53 to 61 in 7d20b25
|
…middleware for full support
…e REST API registration has been removed
|
Note I've removed the REST API integration for now, as we'll need to support this in the middleware first and that may not be ready by the time we submit this to WordPress.org, so removed that and we can come back to that later. For reference when we need this again, removed that in d180247 |
Description of the Change
This PR adds disconnect functionality to the Jobber integration, allowing users to disconnect their Jobber account from WordPress. The implementation includes:
Disconnectclass that handles both UI-initiated and middleware-initiated disconnects/wp-json/jobber/v1/disconnectfor the middleware to calldelete_stored_data()methodThe disconnect functionality can be triggered in two ways:
Note:
Once the middleware is ready, this will be extended to also trigger a request to the middleware to handle the disconnection flow completely.
Closes #19
How to test the Change
Changelog Entry
Credits
Props @dkotter @faisal-alvi
Checklist: