Skip to content

Conversation

@ArthurKnaus
Copy link
Member

Move the onboarding context provider into the onboarding route instead of wrapping it around the whole app.
Reduces risk of breaking things and reduces wrong issue assignments via codeowners.

@ArthurKnaus ArthurKnaus requested a review from a team as a code owner October 2, 2025 08:43
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Oct 2, 2025
`;

export default Onboarding;
export default OnboardingWithProvider;
Copy link
Member

Choose a reason for hiding this comment

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

This is more of a learning question than anything else, but why don't we have to update the imports for this anywhere? Is this some automatic import regardless of object name or something?

Copy link
Member Author

@ArthurKnaus ArthurKnaus Oct 2, 2025

Choose a reason for hiding this comment

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

default imports / exports ignore naming
I could import this as import Foo from 'sentry/views/onboarding/onboarding'

Copy link
Member

Choose a reason for hiding this comment

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

Nice, thank you

Copy link
Member

@priscilawebdev priscilawebdev left a comment

Choose a reason for hiding this comment

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

I believe the onboarding context was originally made global because data was shared between onboarding (new users) and project creation. I double-checked, and it’s now only used in the onboarding pages/hooks. We can safely remove it from this file
as well.

Good update! thank you 🙌

@codecov
Copy link

codecov bot commented Oct 8, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #100770      +/-   ##
===========================================
- Coverage   81.10%    81.10%   -0.01%     
===========================================
  Files        8666      8666              
  Lines      384544    384543       -1     
  Branches    24269     24269              
===========================================
- Hits       311867    311866       -1     
  Misses      72332     72332              
  Partials      345       345              

})}
/>
)}
</GettingStartedLayout>
Copy link
Contributor

Choose a reason for hiding this comment

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

Bug: Context Removal Causes Child Component Failures

Removing the OnboardingContextProvider from GettingStarted may cause runtime errors. If ProjectInstallPlatform or its children use useOnboardingContext(), the missing context will lead to crashes.

Fix in Cursor Fix in Web

@ArthurKnaus ArthurKnaus merged commit dab07bb into master Oct 8, 2025
47 checks passed
@ArthurKnaus ArthurKnaus deleted the aknaus/ref/onboarding/move-onboarding-context-into-onboarding branch October 8, 2025 11:47
@github-actions github-actions bot locked and limited conversation to collaborators Oct 23, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants