Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[MEP][AJO] POC to integrate AJO with MEP #3654
base: stage
Are you sure you want to change the base?
[MEP][AJO] POC to integrate AJO with MEP #3654
Changes from 4 commits
6d9e9ef
453306d
e6a3e2e
4bf24be
1ac0865
147b7db
aca09e6
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is there another way to do this? I am not particularly fond of having a hardcoded string for a path in the utils/utils.js file that is used by all consumers.
For instance, you could author custom page metadata within the metadatablock on a page by page basis to allow multiple POC pages
const isPOC = (document.title === '404' && getMetadata('ajoPoc'));
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hi @JasonHowellSlavin, as far as I know, the only way to impact the metadata for the 404 page is by updating the 404.html file via a code change. I tried authoring the metadata for the fragment that gets pulled in but that doesn't get applied to the page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@markpadbe so the title check for 404 makes sense, but I don't think we want to lock it to the 1 URL. It should work on all 404 pages right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hi @vivgoodrich, the launch code that triggers the related propositionFetch call as of this week is targeting the /products/photoshop/123.html page. That could change, but it won't work on other pages unless that is also updated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I hear ya, but I think we want the POC to be able to work on more pages. Otherwise we'll have to do a PR later just to enable this later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, but I've left open the option to test ajo on other pages by including including getMepEnablement('ajo') on line 30. It won't work on the 404 page because there isn't a way (that I'm aware of) to update the metadata on that page without a code update, but it would work on other pages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would a
queryParam
orhashParam
work here and allow testing on all types of 404 pages? Or is there a reason that will not work as well?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@JasonHowellSlavin, I just got the ok to require a queryParam for the POC and I've updated the code. thanks.