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

Make the new feature search page the default #4391

Merged
merged 2 commits into from
Sep 24, 2024

Conversation

jrobbins
Copy link
Collaborator

I believe that we have checked off everything that we had in mind for this feature, so it is time to finally make it the default this week.

In this PR:

  • Route traffic to the new feature list page at /features
  • Redirect from /newfeatures to /features
  • Move old feature list to /oldfeatures
  • Update banner links, but keep them, and de-emphasize the link back to the old page.

@@ -358,7 +358,8 @@ export class ChromedashApp extends LitElement {
this.pageComponent.showQuery = false;
this.pageComponent.rawQuery = parseRawQuery(ctx.querystring);
});
page('/newfeatures', ctx => {
page('/newfeatures', () => page.redirect('/features'));
page('/features', ctx => {
if (!this.setupNewPage(ctx, 'chromedash-all-features-page', true)) return;
this.pageComponent.user = this.user;
this.pageComponent.rawQuery = parseRawQuery(ctx.querystring);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Lets rename the flag this.pageComponent.isNewfeaturesPage = true; to this.pageComponent.isFeaturesPage = true;

@@ -358,7 +358,8 @@ export class ChromedashApp extends LitElement {
this.pageComponent.showQuery = false;
this.pageComponent.rawQuery = parseRawQuery(ctx.querystring);
});
page('/newfeatures', ctx => {
page('/newfeatures', () => page.redirect('/features'));
page('/features', ctx => {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Question about this - I know the old /features page was not a part of SPA. Is that the reason why it is not routed here before? e.g. there was no page('/features', ctx => {...

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes, exactly. And, now the old page is at /oldfeatures but that is not in the SPA routing because it is still an MPA page.

@jrobbins jrobbins merged commit 6f2a373 into main Sep 24, 2024
7 checks passed
@jrobbins jrobbins deleted the 20240923-make-new-search-the-default branch September 24, 2024 18:03
DanielRyanSmith pushed a commit that referenced this pull request Sep 26, 2024
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