Skip to content

Rename Site Health check modules for language and consistency #423

New issue

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

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

Already on GitHub? # to your account

Merged
merged 6 commits into from
Aug 14, 2022
Merged

Rename Site Health check modules for language and consistency #423

merged 6 commits into from
Aug 14, 2022

Conversation

OllieJones
Copy link
Contributor

@OllieJones OllieJones commented Jul 8, 2022

Summary

Updated the (English) language captions in the Settings panel.

Changed the site-health slugs to, for example, to autoloaded-options-health-check to audit-autoloaded-options.

Made corresponding changes in the unit-test directory and file names.

(This very easy dev task will help me ensure I know how to drive the PR workflow.)

Fixes #326

Relevant technical choices

Trivial editing of the strucutured comments at the top of four load.php files

Checklist

  • PR has either [Focus] or Infrastructure label.
  • PR has a [Type] label.
  • PR has a milestone or the no milestone label.

@mxbclang mxbclang added Infrastructure Issues for the overall performance plugin infrastructure [Type] Enhancement A suggestion for improvement of an existing feature labels Jul 11, 2022
@mxbclang mxbclang added this to the 1.3.0 milestone Jul 11, 2022
@OllieJones OllieJones marked this pull request as ready for review July 11, 2022 12:18
Copy link
Contributor

@mxbclang mxbclang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@mukeshpanchal27 mukeshpanchal27 added the no milestone PRs that do not have a defined milestone for release label Jul 11, 2022
@mukeshpanchal27
Copy link
Member

IMO plugin creates a folder structure based on the module name, so if we change the module name, then it does not match.

@mukeshpanchal27 mukeshpanchal27 removed the no milestone PRs that do not have a defined milestone for release label Jul 13, 2022
@mxbclang
Copy link
Contributor

@felixarntz Tagging you in to take a quick look at this one based on @mukeshpanchal27's comment above.

@mxbclang mxbclang requested a review from felixarntz July 13, 2022 13:35
Copy link
Member

@felixarntz felixarntz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @OllieJones! Potentially we should rename the module slugs (i.e. move the directories) as well?

Copy link
Member

@felixarntz felixarntz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After further thought, I tend to agree with @mukeshpanchal27's feedback in #423 (comment) that we should probably rename the modules as a whole.

@OllieJones Could you rename the module directories and references to it?

This is not extremely critical and the deadline for release PRs is today, so I'm going to remove this one for now, we can target it for 1.4.0.

@felixarntz felixarntz modified the milestones: 1.3.0, 1.4.0 Jul 14, 2022
Backmerge latest changes.
@mukeshpanchal27
Copy link
Member

@OllieJones We are two weeks away from the 1.4.0 release. Could you follow up on that? It would be great. Thank you!

@OllieJones
Copy link
Contributor Author

I will do this.

I need clarification. I think you want, for example, the Autoloaded Options Health Check module to be placed in the directory .../modules/health-check/autoloaded-options rather than .../modules/site-health/audit-autoloaded-options. Is that correct?

@mukeshpanchal27
Copy link
Member

It should be .../modules/site-health/autoloaded-options-health-check rather than .../modules/site-health/audit-autoloaded-options similar for other modules. Does that make sense?

…ull-page-cache to full-page-cache-health-check. Change directory and file names under tests to match.
@OllieJones
Copy link
Contributor Author

OllieJones commented Aug 2, 2022

I made the changes requested by @mukeshpanchal27 and @felixarntz .

Copy link
Member

@mukeshpanchal27 mukeshpanchal27 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@felixarntz felixarntz mentioned this pull request Aug 8, 2022
3 tasks
Copy link
Member

@felixarntz felixarntz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@OllieJones Apologies, I am now seeing another problem here regarding the module renaming (even though I originally proposed it): Renaming the modules is problematic since it may already be stored in the sites' DB options, or developers may use the module slugs in the filter. So it would result in breakage currently where if a site had one of the remained modules active, it would no longer be active after the update, which we must avoid.

If we want to go through with the module slug/directory changes, at a minimum we would need to add logic to retrieving the option value so that it migrates the old values to the new ones. But even that would not be 100% proof.

So I think (sorry again about that) it would be best to go back to your previous implementation where you only adjust the module names themselves. One thing missing here then is to also update the CODEOWNERS file comments where these same names are referenced accordingly. Also see the related #465 PR - we need to decide which one of these naming conventions to go with. cc @bethanylang

@mxbclang
Copy link
Contributor

mxbclang commented Aug 9, 2022

Thanks @felixarntz! My personal preference would be to go with @OllieJones' approach and add "Health Check" to the end of each appropriate module title in order to distinguish those from the other, non-Health Check modules, but let me know what you think.

@felixarntz
Copy link
Member

@bethanylang Thanks, SGTM.

@OllieJones Can you revert the directory name changes in this PR so that it's back to only changes to the actual module titles?

I'll move this out of the 1.4.0 milestone for now since it's not ready yet, but if it gets ready tomorrow, we could potentially still include it in this release.

@felixarntz felixarntz modified the milestones: 1.4.0, 1.5.0 Aug 10, 2022
… audit-full-page-cache to full-page-cache-health-check. Change directory and file names under tests to match."

This reverts commit 8cf5013.
Undo module slug name changes per Felix Arntz's request at #423 (comment)
@OllieJones
Copy link
Contributor Author

The module slugs (directory names) are now reverted. Should be ready to merge.

@mxbclang
Copy link
Contributor

Thanks, @OllieJones! There are still changes that need to be made per @felixarntz's requests here: https://github.com/WordPress/performance/pull/423/files/8cf50133dacc686c153dfb632bfb0feb6369a497. Can you make those updates when you get a moment, as well? Then this should be ready to merge and I can update #465. Thanks!

@felixarntz
Copy link
Member

@bethanylang I think actually everything has been addressed now. Since we're only changing the module names here vs the slugs, no migration of the option should happen.

I think we're good to merge this and then update #465.

Copy link
Member

@felixarntz felixarntz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, thank you @OllieJones!

@felixarntz felixarntz changed the base branch from trunk to release/1.4.0 August 14, 2022 08:24
@felixarntz felixarntz modified the milestones: 1.5.0, 1.4.0 Aug 14, 2022
@felixarntz felixarntz changed the title #326 Update Settings language for health checks. Rename Site Health check modules for language and consistency Aug 14, 2022
@felixarntz felixarntz merged commit 10aefe4 into WordPress:release/1.4.0 Aug 14, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Infrastructure Issues for the overall performance plugin infrastructure [Type] Enhancement A suggestion for improvement of an existing feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update Settings language for health checks
5 participants