Comments (3)
This package (which we haven't advertised much for a reason) is only meant to be used by certain users of React 16 and actually also 17, since React 17 doesn't automatically batch external synchronous updates. Users of React 18, don't need to use it, ofc (and neither do most users of React 16 and 17 TBH).
However, since the core package supports React >=16.8.0 then this package could still be relevant to some users.
Although, TBH I would really rather to get rid of this package completely. I would like to know what @voliva thoughts are on this topic. Personally, as much as I hate it, I think that we should keep it until we drop support for React 16 and 17.
Please bear in mind that @react-rxjs/core
doesn't have this as one of its dependencies, so unless someone intentionally installs the package into their project and imports and uses the batchUpdates
pipeable operator, then this package can not cause any unwanted bugs. Also, I have a hard time imagining how the batchUpdates
pipeable operator can cause unwanted bugs, but I guess that possible, yep.
from react-rxjs.
Yes, I think that we should keep it around as long as this library supports React 16.
It's an opt-in feature for consumers that might want to use it on React 17-, and it's published as a separate package.
from react-rxjs.
It is true that I did not find any documentation on it afaik but I was curious about the project and digging into the source code, which raised some questions.
That is a fair and clear enough answer, thank you.
from react-rxjs.
Related Issues (20)
- Incompatible with tsx HOT 3
- Typescript integration issues HOT 2
- doc: The link to bundlephobia is an old package HOT 1
- <Subscribe> not working HOT 1
- Uncaught Error: Missing Subscribe
- Proposal to support event handlers HOT 1
- Uncaught Error: Missing Subscribe HOT 2
- Observable emitting error should not cause infinite loop on Subscribe HOT 1
- Question - Todo App Demo
- Testing a signal HOT 1
- Are there any projects that use React-RxJS?
- hook returned by bind(functionAcceptingArrayReturningAsyncObservable$) should not cause infinite render loop HOT 2
- takeUntil operator cannot complete a StateObservable HOT 1
- Server side rendering is missing `getServerSnapshot` HOT 2
- [BUG] bind is returning an array when an Object is passed through the observer. HOT 1
- Use native react use-sync-external-store instead of package HOT 2
- bind hook only firing once with scan and aggregated map HOT 3
- TypeScript moduleResolution: NodeNext expects core.es2017.d.ts types file
- Subscribe incorrectly rendering fallback on initial mount HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from react-rxjs.