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
Remove immediate_hydration config - Pro always hydrates immediately (#1997)
Why
Simplify configuration for pro users. Still allows override at react_component level.
Summary
Removed visual warning badges for Pro features, made immediate
hydration automatic for Pro users, and removed global config option.
Key improvements
- Automatic immediate hydration for Pro users (no config needed)
- Rails logger warnings replace visual badges for better UX
- Component-level overrides still supported via helper parameters
Impact
- Existing: Pro users unchanged; immediate hydration auto-enabled
- New: Simpler config; non-Pro get warnings in logs, not UI
Risks
Breaking: config.immediate_hydration removed from initializers
(see CHANGELOG migration steps). Security: None.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,12 +51,26 @@ Changes since the last non-beta release.
51
51
52
52
-**Removed Pro Warning Badge**: Removed the visual warning badge that appeared when non-Pro users attempted to enable Pro-only features like `immediate_hydration`. Pro features are now silently disabled when a Pro license is not available, providing a cleaner user experience without intrusive warning banners. [PR 1993](https://github.com/shakacode/react_on_rails/pull/1993) by [AbanoubGhadban](https://github.com/AbanoubGhadban).
53
53
54
+
-**`immediate_hydration` now automatically enabled for Pro users**: The `config.immediate_hydration` configuration option has been removed. Immediate hydration is now automatically enabled for React on Rails Pro users and disabled for non-Pro users, simplifying configuration while providing optimal performance by default. Component-level overrides are still supported via the `immediate_hydration` parameter on `react_component`, `redux_store`, and `stream_react_component` helpers. [PR 1997](https://github.com/shakacode/react_on_rails/pull/1997) by [AbanoubGhadban](https://github.com/AbanoubGhadban).
55
+
54
56
#### Bug Fixes
55
57
56
58
-**Use as Git dependency**: All packages can now be installed as Git dependencies. This is useful for development and testing purposes. See [CONTRIBUTING.md](./CONTRIBUTING.md#git-dependencies) for documentation. [PR #1873](https://github.com/shakacode/react_on_rails/pull/1873) by [alexeyr-ci2](https://github.com/alexeyr-ci2).
57
59
58
60
#### Breaking Changes
59
61
62
+
-**`config.immediate_hydration` configuration removed**: The `config.immediate_hydration` setting in `config/initializers/react_on_rails.rb` has been removed. Immediate hydration is now automatically enabled for React on Rails Pro users and automatically disabled for non-Pro users.
63
+
64
+
**Migration steps:**
65
+
66
+
- Remove any `config.immediate_hydration = true` or `config.immediate_hydration = false` lines from your `config/initializers/react_on_rails.rb` file
67
+
- Pro users: No action needed - immediate hydration is now enabled automatically for optimal performance
68
+
- Non-Pro users: No action needed - standard hydration behavior continues to work as before
69
+
- Component-level overrides: You can still override behavior per-component using `react_component("MyComponent", immediate_hydration: false)` or `redux_store("MyStore", immediate_hydration: true)`
70
+
- If a non-Pro user explicitly sets `immediate_hydration: true` on a component, a warning will be logged and the component will fall back to standard hydration
71
+
72
+
[PR 1997](https://github.com/shakacode/react_on_rails/pull/1997) by [AbanoubGhadban](https://github.com/AbanoubGhadban).
73
+
60
74
-**React on Rails Core Package**: Several Pro-only methods have been removed from the core package and are now exclusively available in the `react-on-rails-pro` package. If you're using any of the following methods, you'll need to migrate to React on Rails Pro:
0 commit comments