-
Notifications
You must be signed in to change notification settings - Fork 821
Jetpack Script Data: Cleanup unused host data and functionality, keeping data close to source #44133
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
base: trunk
Are you sure you want to change the base?
Conversation
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
Interested in more tips and information?
|
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
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 🤖 Follow this PR Review Process:
If you have questions about anything, reach out in #jetpack-developers for guidance! Jetpack plugin: The Jetpack plugin has different release cadences depending on the platform:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Mu Wpcom plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. |
Code Coverage SummaryCoverage changed in 6 files. Only the first 5 are listed here.
|
86393b7
to
787e04c
Compare
fae9b7b
to
17de626
Compare
3474715
to
6b5994b
Compare
Fixes VULCAN-212
Proposed changes:
jetpack_admin_js_script_data
, is now added to Assets directly (given that it exists for the public script now as well - so this is also more consistent).Other information:
Jetpack product discussion
VULCAN-115
Does this pull request change what data or activity we track or use?
No.
Testing instructions:
Code review - the removed functions were not in use, a code check within the monorepo should confirm that.
In terms of the host data moved into the Assets package, follow the testing instructions in the following PR (where related to differences between WoA / Simple / self-hosted sites):
JetpackScriptData
object has asite
property, which has ahost
property (on Jurassic Ninja that will be 'atomic'). You may need to 'Get Started' from the Jetpack Social dashboard page too - and should be able to confirm the script data is present on that dashboard too. This script information should be showing generally on a WoA, and Simple site as well.Also, follow the testing instructions in this PR to ensure the WoA functionality works as expected: