Skip to content

Ref(Sample): Add existing bundled playgroundscreen into sample app#5778

Open
lucas-zimerman wants to merge 2 commits intomainfrom
lz/playground
Open

Ref(Sample): Add existing bundled playgroundscreen into sample app#5778
lucas-zimerman wants to merge 2 commits intomainfrom
lz/playground

Conversation

@lucas-zimerman
Copy link
Collaborator

@lucas-zimerman lucas-zimerman commented Mar 5, 2026

📢 Type of change

  • Bugfix
  • New feature
  • Enhancement
  • Refactoring

📜 Description

💡 Motivation and Context

On the playground area, I added a new button to interact with the existing playground that exists within the SDK.

image

💚 How did you test it?

Running the sample app

📝 Checklist

  • I added tests to verify changes
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled
  • I updated the docs if needed.
  • I updated the wizard if needed.
  • All tests passing
  • No breaking changes

🔮 Next steps

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

<BottomTabNavigator.Screen
name="PlaygroundTab"
component={getPlaygroundTab()}
component={getPlaygroundTab(StackNavigator)}
Copy link

Choose a reason for hiding this comment

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

Argument passed to getPlaygroundTab is silently ignored

Low Severity

getPlaygroundTab(StackNavigator) passes StackNavigator as an argument, but getPlaygroundTab is defined with no parameters — so the argument is silently ignored. The other two tab factories (getErrorsTab, getPerformanceTab) accept a Navigator: TypedNavigator<any, any> parameter and use it to create nested navigators, but getPlaygroundTab was never updated to match. This looks like an incomplete refactoring step and could mislead future developers.

Additional Locations (1)

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant