-
Notifications
You must be signed in to change notification settings - Fork 2k
WIP: PoC cleaning up dashboard redirects. #107755
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
base: trunk
Are you sure you want to change the base?
Conversation
Jetpack Cloud live (direct link)
Automattic for Agencies live (direct link)
|
|
This PR modifies the release build for the following Calypso Apps: For info about this notification, see here: PCYsg-OT6-p2
To test WordPress.com changes, run |
|
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: App Entrypoints (~6240 bytes added 📈 [gzipped]) DetailsCommon code that is always downloaded and parsed every time the app is loaded, no matter which route is used. Sections (~9123 bytes added 📈 [gzipped]) DetailsSections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to. Async-loaded Components (~8526 bytes added 📈 [gzipped]) DetailsReact components that are loaded lazily, when a certain part of UI is displayed for the first time. Legend What is parsed and gzip size?Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory. Generated by performance advisor bot at iscalypsofastyet.com. |
8568857 to
addd9a5
Compare
fushar
left a comment
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.
Apologies if I'm missing something, but wouldn't this be so much simpler if we just modify the existing dashboardLink() / redirectToDashboardLink() to return CIAB URL if we're on CIAB HD?
This creates a unified way for going from the /ciab or /v2 dashboards into Stepper and back again. Previously, we had issues with certain redirect paths being hardcoded. Now everything is generic. We've added a dashboard= query param which is used to contruct the final redirect url. This query param will also be available if we need to do any branding changes in Stepper. For example, if we're coming into Stepper from /ciab, we want to show the Woo branding instead of WordPress.com. Any places where we don't specific provide dashboard & redirect_to will fall back to the existing behavior.
addd9a5 to
db6753c
Compare
db6753c to
840ee76
Compare
Part of #
Proposed Changes
This is experimenting with a more unified way of handling redirects in cases where a user enters the Stepper from either the
/ciabor/v2dashboards and then needs to be redirected back. The goal is to come up with an easy way to handle those redirects that will work regardless of which dashboard the user was on. That way we don't have to worry about/ciabusers being redirected to/v2or vice-versa.We're adding a new
dashboard=query param (currently should only beciaborv2) in addition to the existingredirect_toparam. Those two params together will be used to construct the full url that the user is redirected to.Testing Instructions
TBD
Pre-merge Checklist