You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default realtime backend was hardcoded to Electric. This adds a REALTIME_BACKEND_DEFAULT env var (electric | native | shadow, default electric) that chooses the backend for any environment whose org has no realtimeBackend override. Behavior is unchanged unless you set it; per-org overrides still win.
The default is applied at every point where the per-org flag falls through: the initial value, the flag lookup default, and the error fallback.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Added the validated REALTIME_BACKEND_DEFAULT environment variable, supporting electric, native, and shadow, with electric as the default. Updated realtime backend resolution to use this value for initialization, feature-flag defaults, and error fallbacks. Documented the new environment variable and its behavior.
🚥 Pre-merge checks | ✅ 4 | ❌ 1
❌ Failed checks (1 warning)
Check name
Status
Explanation
Resolution
Description check
⚠️ Warning
The description only includes a summary and omits required template sections like Closes #issue, checklist, testing, changelog, and screenshots.
Add the missing template sections: Closes #issue, checklist items, Testing steps, Changelog, and Screenshots or explicit N/A entries.
✅ Passed checks (4 passed)
Check name
Status
Explanation
Docstring Coverage
✅ Passed
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check
✅ Passed
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
✅ Passed
Check skipped because no linked issues were found for this pull request.
Title check
✅ Passed
The title clearly states the main change: making the default realtime backend configurable.
✨ Finishing Touches📝 Generate docstrings
Create stacked PR
Commit on current branch
🧪 Generate unit tests (beta)
Create PR with unit tests
Commit unit tests in branch feature/tri-11906-add-realtime_backend_default-env-var-to-set-the-default
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.
This file contains hidden or 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
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.
Summary
The default realtime backend was hardcoded to Electric. This adds a
REALTIME_BACKEND_DEFAULTenv var (electric|native|shadow, defaultelectric) that chooses the backend for any environment whose org has norealtimeBackendoverride. Behavior is unchanged unless you set it; per-org overrides still win.The default is applied at every point where the per-org flag falls through: the initial value, the flag lookup default, and the error fallback.