feat(desktop): enable v2 by default in dev#3883
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdds a development environment override to the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Review rate limit: 3/8 reviews remaining, refill in 30 minutes and 22 seconds.Comment |
🧹 Preview Cleanup CompleteThe following preview resources have been cleaned up:
Thank you for your contribution! 🎉 |
The upstream change at superset-sh#3883 force-enables v2 in dev mode, but v2 requires Superset cloud auth to start the host-service. For local development without a cloud account, this hides v1 workspaces and blocks usage entirely. Restore the original PostHog flag + opt-in gate so v1 remains accessible by default.
Description
Related Issues
Type of Change
Testing
Screenshots (if applicable)
Additional Notes
Summary by cubic
Turn on v2 Cloud by default in development. In
NODE_ENV=development,useIsV2CloudEnabledreturnsisV2CloudEnabled: trueandisRemoteV2Enabled: true, bypassing the PostHog flag and local opt-in (no change in production).Written for commit db1ff85. Summary will update on new commits. Review in cubic
Summary by CodeRabbit