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

feat: fix prequery suggestion highlight container #380

Merged
merged 1 commit into from
Mar 11, 2024

Conversation

katrinan029
Copy link
Contributor

@katrinan029 katrinan029 commented Mar 7, 2024

Fix the margins for when the prequery suggestion is highlighted to match B2C.

https://2u-internal.atlassian.net/browse/ENT-8593

UI Changes

before after
Screenshot 2024-03-07 at 10 26 49 AM Screenshot 2024-03-07 at 10 34 06 AM

Merge checklist:

  • Evaluate how your changes will impact existing consumers (e.g., frontend-app-learner-portal-enterprise, frontend-app-admin-portal, and frontend-app-enterprise-public-catalog). Will consumers safely be able to upgrade to this change without any breaking changes?
  • Ensure your commit message follows the semantic-release conventional commit message format. If your changes include a breaking change, ensure your commit message is explicitly marked as a BREAKING CHANGE so the NPM package is released as such.
  • Once CI is passing, verify the package versions that Lerna will increment to in the Github Action CI workflow logs.
    • Note: This may be found in the "Preview Updated Versions (dry run)" step in the Github Action CI workflow logs.

Post merge:

  • Verify Lerna created a release commit (e.g., chore(release): publish) that incremented versions in relevant package.json and CHANGELOG files, and created Git tags for those versions.
  • Run the Publish from package.json Github Action workflow to publish these new package versions to NPM.
    • This may be triggered by clicking the "Run workflow" option for the master branch.
  • Verify the new package versions were published to NPM (i.e., npm view <package_name> versions --json).
    • Note: There may be a slight delay between when the workflow finished and when NPM reports the package version as being published. If it doesn't appear right away in the above command, try again in a few minutes.

@katrinan029 katrinan029 marked this pull request as ready for review March 7, 2024 18:40
Copy link

codecov bot commented Mar 7, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.67%. Comparing base (dcb962f) to head (46117b8).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #380   +/-   ##
=======================================
  Coverage   78.67%   78.67%           
=======================================
  Files          35       35           
  Lines         694      694           
  Branches      177      177           
=======================================
  Hits          546      546           
  Misses        135      135           
  Partials       13       13           

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dcb962f...46117b8. Read the comment docs.

@katrinan029 katrinan029 requested a review from a team March 7, 2024 19:27
@katrinan029 katrinan029 merged commit d54a0c7 into master Mar 11, 2024
19 checks passed
@katrinan029 katrinan029 deleted the knguyen2/ent-8593 branch March 11, 2024 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants