Repository navigation
docs(android): Harmonize Android Navigation and Jetpack Compose docs - #19850
0xadam-brown wants to merge 2 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
942d73e to
62f147e
Compare
Commit moves navigation-specific content from the Android Jetpack Compose page to the corresponding Navigation page. It also refines the Navigation page for consistency and correctness.
62f147e to
f8f5b04
Compare
|
The plan checks full page loads and in-app navigations on the two rewritten Android pages. It also checks client errors on those pages and on sibling Android integration pages. An issue escalates when those pages stop loading or client errors rise. Services: Mention PlanWhat changedReaders of the Jetpack Compose page no longer see Navigation install steps. That page now links to the Navigation page for that setup. Readers of the Navigation page now see Jetpack Compose Navigation 2 install, configure, and verify steps. Navigation 3 now records five back-stack entries instead of ten. The change is live after RiskBroken MDX can fail static generation or page render. Readers then miss the page. The old Compose heading Intended effectBoth pages keep serving after deploy. Sampled page load and navigation spans on those URLs stay above zero.
Traces use a 30% sample rate. Counts below are sampled spans, not full traffic.
Regression watchThis diff can break render of these two pages or sibling Android integration pages. Watch client errors on those URLs. Watch page load duration on the larger Navigation page.
Not observableWhether the moved install snippets are correct. Whether old hash links to |
DESCRIBE YOUR PR
Tell us what you're changing and why. If your PR resolves an issue, please link it so it closes automatically.
PR moves navigation-specific content from the Android Jetpack Compose page to the corresponding Navigation page. It also refines the Navigation page for consistency and correctness.
Work is a follow-up to the Nav3 docs recently introduced in #19804.
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace
YYYY-MM-DDwith the due date. You can update this information later by editing the PR description.SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES