-
Notifications
You must be signed in to change notification settings - Fork 2k
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
wpcom-proxy-request: Return Promise if no callback specified (Take 3) #39825
wpcom-proxy-request: Return Promise if no callback specified (Take 3) #39825
Conversation
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: App Entrypoints (~315 bytes added 📈 [gzipped])
Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used. 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. Generated by performance advisor bot at iscalypsofastyet.com. |
jest.mock( 'wpcom-proxy-request', () => ( { | ||
__esModule: true, | ||
default: jest.fn(), | ||
requestAllBlogsAccess: jest.fn( () => Promise.resolve() ), | ||
} ) ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A centralized set of generic controls for wpcom-proxy-request and generic fetch could make this testing easier.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Follow-up material maybe? 😬
I've pushed fixes for the issues introduced by merge, the auth store work was incompatible with the other changes from this branch. This should be ready to land now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Third time's a charm! 🍀 🤞
Reverts #39823
Take 3 of #39683:
Conflicting changes had been merged in the interim. I've updated the imports to fix the issue from #39722