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

MWPW-133726 add smart redirects for (temporary) client-side redirects #257

Merged
merged 1 commit into from
Nov 5, 2024

Conversation

trieloff
Copy link
Contributor

@trieloff trieloff commented Oct 16, 2024

  • add smart redirects for (temporary) client-side redirects

this is a port of adobe/helix-website#671 and adobe/helix-website#670
from www.aem.live to bacom, see discussion in https://adobe.enterprise.slack.com/archives/C0749KS9F8X

Resolves: MWPW-133726

Test URLs
Simple Redirect

One parameter redirect

Multi-parameter redirect

Different order parameter redirect

Copy link

aem-code-sync bot commented Oct 16, 2024

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

  • Re-run PSI checks
  • Re-sync branch
Commits

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.70%. Comparing base (94a0e5c) to head (fc1262d).

Additional details and impacted files
@@           Coverage Diff           @@
##            stage     #257   +/-   ##
=======================================
  Coverage   96.70%   96.70%           
=======================================
  Files          12       12           
  Lines        1335     1335           
=======================================
  Hits         1291     1291           
  Misses         44       44           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@mokimo mokimo left a comment

Choose a reason for hiding this comment

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

Cool to see this proceeding, I know it's been discussed a lot

Copy link
Contributor

@JasonHowellSlavin JasonHowellSlavin left a comment

Choose a reason for hiding this comment

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

Should we port over the unit tests as well, or does that seem unnecessary since this PR points to the location of those tests?

Copy link
Contributor

@meganthecoder meganthecoder left a comment

Choose a reason for hiding this comment

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

Hi @trieloff , Thanks for contributing! A few of notes:

  1. I agree with @JasonHowellSlavin . If there's the possibility of needing maintenance/modifications in this repo, it should probably include the unit tests.
  2. We usually link a jira ticket in the description. Is there a jira ticket or issue number associated with this feature?
  3. We can contact the team who manages access or we can create the file for you. Just let us know. Our QE will need something to verify, so we'll want to get that set up before merging.

@amol-anand
Copy link
Contributor

amol-anand commented Oct 21, 2024

We usually link a jira ticket in the description. Is there a jira ticket or issue number associated with this feature?
https://adobe.enterprise.slack.com/archives/C0749KS9F8X

This slack thread has the entire discussion. Not sure if someone put that into a JIRA ticket.

Should we port over the unit tests as well, or does that seem unnecessary since this PR points to the location of those tests?

Like you mentioned, since we are using a different sheet (endpoint), it seems unnecessary to add unit tests for this, since the tests would need a similar test sheet for testing it out anyways.

We can contact the team who manages access or we can create the file for you. Just let us know. Our QE will need something to verify, so we'll want to get that set up before merging.

Whatever is easier for you. If someone can create the file and preview it, we can then test the functionality in this feature branch url.

Copy link
Contributor

@meganthecoder meganthecoder left a comment

Choose a reason for hiding this comment

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

LGTM - I've added smart-redirects.json and included some examples (based on the unit tests) in the description.

@meganthecoder meganthecoder changed the title feat(smart-redirects): add smart redirects for (temporary) client-side redirects MWPW-133726 add smart redirects for (temporary) client-side redirects Oct 21, 2024
@JackySun9 JackySun9 added verified it's been E2E tested by someone (that isn't the PR requestor) ready for stage labels Oct 22, 2024
@trieloff
Copy link
Contributor Author

Thanks for driving this forward in my absence, @amol-anand

@meganthecoder
Copy link
Contributor

Release planned for Tuesday 11/5

@meganthecoder meganthecoder merged commit fa44435 into stage Nov 5, 2024
7 of 8 checks passed
@meganthecoder meganthecoder deleted the smart-redirects branch November 5, 2024 18:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready for stage verified it's been E2E tested by someone (that isn't the PR requestor)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants