-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
perf: Use one PageWrapper instance for every non-settings / non-bookings page in App Router #18747
Draft
hbjORbj
wants to merge
19
commits into
chore/removing-WithLayout-from-bookings-status-page
Choose a base branch
from
chore/removing-WithLayout-from-more-multiple-pages
base: chore/removing-WithLayout-from-bookings-status-page
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…yout-from-more-multiple-pages
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Skipped Deployments
|
hbjORbj
changed the base branch from
main
to
chore/removing-WithLayout-from-bookings-status-page
January 18, 2025 23:28
hbjORbj
changed the base branch from
chore/removing-WithLayout-from-bookings-status-page
to
main
January 18, 2025 23:28
hbjORbj
changed the title
chore: removing withlayout from more multiple pages
chore: Remove WithLayout from availability, event-types, and insights pages
Jan 18, 2025
Graphite Automations"Add consumer team as reviewer" took an action on this PR • (01/18/25)1 reviewer was added to this PR based on Keith Williams's automation. "Add foundation team as reviewer" took an action on this PR • (01/18/25)1 reviewer was added to this PR based on Keith Williams's automation. |
E2E results are ready! |
hbjORbj
changed the title
chore: Remove WithLayout from availability, event-types, and insights pages
chore: Use one PageWrapper instance for every non-settings / non-bookings page in App Router
Jan 19, 2025
…to chore/removing-WithLayout-from-more-multiple-pages
hbjORbj
changed the base branch from
main
to
chore/removing-WithLayout-from-bookings-status-page
January 19, 2025 19:34
hbjORbj
changed the title
chore: Use one PageWrapper instance for every non-settings / non-bookings page in App Router
perf: Use one PageWrapper instance for every non-settings / non-bookings page in App Router
Jan 19, 2025
hbjORbj
added
the
performance
area: performance, page load, slow, slow endpoints, loading screen, unresponsive
label
Jan 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
consumer
core
area: core, team members only
foundation
performance
area: performance, page load, slow, slow endpoints, loading screen, unresponsive
ready-for-e2e
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.
What does this PR do?
WithLayout
and relying on a single layout file. We need to migrate all routes that useWithLayout
into(use-page-wrapper)
route group.WithLayout
from/bookings/[status]
page + 8 low-risk single pages #18737 is merged intomain
, rebase this branch on top ofmain
Mandatory Tasks (DO NOT REMOVE)
How should this be tested?