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

324 tailwindify the errors and notices in the related keyphrase suggestions modal #21815

Conversation

vraja-pro
Copy link
Contributor

@vraja-pro vraja-pro commented Nov 12, 2024

Context

Summary

This PR can be summarized in the following changelog entry:

  • Implements new design for the warnings and errors in the related keyphrases suggestions modal.
  • [@yoast/related-keyphrase-suggestions 0.1.0] Changes the design of the warnings and errors alerts in the related keyphrase suggestions.

Relevant technical choices:

  • The pending notice is dropped since we have the loading table.
  • relatedKeyphrases is a prop coming from Premium, checking for relatedKeyphrases includes checking for premium.

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

  • Check alerts for:
    • When there are more than 4 related keyphrases selected.
    • When the request failed
    • When there are no suggestions in the result
    • When the reaching the max requests for semrush:
      • The country selector should be hidden.
      • The button should have a lint to semrush upsell page.
      • Without premium, check that the premium upsell is hidden.

Relevant test scenarios

  • Changes should be tested with the browser console open
  • Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
  • Changes should be tested on different editors (Default Block/Gutenberg/Classic/Elementor/other)
  • Changes should be tested on different browsers
  • Changes should be tested on multisite

Test instructions for QA when the code is in the RC

  • QA should use the same steps as above.

QA can test this PR by following these steps:

Impact check

This PR affects the following parts of the plugin, which may require extra testing:

UI changes

  • This PR changes the UI in the plugin. I have added the 'UI change' label to this PR.

Other environments

  • This PR also affects Shopify. I have added a changelog entry starting with [shopify-seo], added test instructions for Shopify and attached the Shopify label to this PR.

Documentation

  • I have written documentation for this change. For example, comments in the Relevant technical choices, comments in the code, documentation on Confluence / shared Google Drive / Yoast developer portal, or other.

Quality assurance

  • I have tested this code to the best of my abilities.
  • During testing, I had activated all plugins that Yoast SEO provides integrations for.
  • I have added unit tests to verify the code works as intended.
  • If any part of the code is behind a feature flag, my test instructions also cover cases where the feature flag is switched off.
  • I have written this PR in accordance with my team's definition of done.
  • I have checked that the base branch is correctly set.

Innovation

  • No innovation project is applicable for this PR.
  • This PR falls under an innovation project. I have attached the innovation label.
  • I have added my hours to the WBSO document.

Fixes Tailwindify the errors and notices in the related keyphrase suggestions modal

@vraja-pro vraja-pro added UI change PRs that result in a change in the UI changelog: enhancement Needs to be included in the 'Enhancements' category in the changelog labels Nov 12, 2024
@vraja-pro vraja-pro force-pushed the 324-tailwindify-the-errors-and-notices-in-the-related-keyphrase-suggestions-modal branch from ec7e7f9 to c2f9424 Compare November 12, 2024 11:04
@coveralls
Copy link

coveralls commented Nov 12, 2024

Pull Request Test Coverage Report for Build e897c7d0b939493858af6978864834fd22861c8b

Details

  • 4 of 6 (66.67%) changed or added relevant lines in 1 file are covered.
  • 6 unchanged lines in 5 files lost coverage.
  • Overall coverage decreased (-0.01%) to 54.665%

Changes Missing Coverage Covered Lines Changed/Added Lines %
packages/js/src/components/SEMrushRelatedKeyphrasesModalContent.js 4 6 66.67%
Files with Coverage Reduction New Missed Lines %
packages/js/src/components/modals/SEMrushLoading.js 1 0.0%
packages/js/src/components/modals/SEMrushMaxRelatedKeyphrases.js 1 0.0%
packages/js/src/components/modals/SEMrushRequestFailed.js 1 0.0%
packages/js/src/containers/SEMrushRelatedKeyphrases.js 1 0.0%
packages/js/src/components/modals/SEMrushLimitReached.js 2 0.0%
Totals Coverage Status
Change from base Build 7cce7dd70502c7f2b8b9e72de389ebde032a2f4e: -0.01%
Covered Lines: 29739
Relevant Lines: 54688

💛 - Coveralls

hide country selector only when semrush limited reached

fix order

add premium to container

reduce complexity
@pls78 pls78 changed the base branch from trunk to feature/plugin-fixes November 21, 2024 15:35
@pls78 pls78 force-pushed the 324-tailwindify-the-errors-and-notices-in-the-related-keyphrase-suggestions-modal branch from 4676325 to 6bcab3b Compare November 21, 2024 16:24
Copy link
Member

@pls78 pls78 left a comment

Choose a reason for hiding this comment

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

CR: ✅
Acc: ⚠️ When a requestEmpty alert is shown, once the modal is closed and is opened again after the keyphrase has been changed, the alert is still visible just before the table is populated. Are we ok with this?

Copy link
Member

@pls78 pls78 left a comment

Choose a reason for hiding this comment

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

Acc: ✅

@pls78 pls78 added this to the feature/plugin-fixes milestone Nov 22, 2024
@pls78 pls78 merged commit b4aded0 into feature/plugin-fixes Nov 22, 2024
16 checks passed
@pls78 pls78 deleted the 324-tailwindify-the-errors-and-notices-in-the-related-keyphrase-suggestions-modal branch November 22, 2024 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog: enhancement Needs to be included in the 'Enhancements' category in the changelog UI change PRs that result in a change in the UI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants