- fix(isolate): use TypeScript unknown to force casting types (ff698ce)
- If you use JavaScript, there are no breaking changes. If you use TypeScript, then from now onwards isolate() returns sink types that are never type "any", but instead returns "unknown". Often it may infer the correct type, but when it cannot infer the type, it will return "unknown" which means you are forced to type cast it to the correct type. This is better than "any", because "any" is like JavaScript and gives little type safety.
- fix(isolate): support TypeScript's strict mode (c8aee41)
- fix(isolate): support TypeScript 3.1 (3e847bb)
- refactor(isolate): move isolate tooling to pnpm (6aea3e7)
- If you use JavaScript, there are no breaking changes. If you use TypeScript, this package may not work anymore with versions of TS below 3.1.
- isolate: adapt sinks so xstream semantics can be applied (77ae9d0)
- isolate: This update changes the contract such that xstream and @cycle/run are now dependencies.
ISSUES CLOSED: #826
- isolate: add `toIsolated` returning a higher order component (fe1efb3)
- isolate: support null scope to disable isolation (2427d76)
- isolate: This is a breaking change only in case you utilized null scopes to perform isolation. Previously null scope would enable isolation using null as the isolation name, and now null scope will just disable isolation. It would be quite a corner case to rely on null scopes, so this will breaking change likely not affect your project, and this new version of isolate is rather safe to upgrade.
- isolate: allow a scopes-per-channel object as second arg (e35b731)
See the changelog for all the rc versions of v2.0.0.
- isolate: fix typings for isolate, accepts any sources (ccd5ec1)
- isolate: update codebase to use TypeScript 2.1 (0ec0980)
- isolate: If you use JavaScript, this will not be a breaking change. If you use TypeScript 2.0, this is a
- isolate: as we are using exclusive TypeScript 2.1 features, only supported in v2.1.
- isolate: update codebase to use TypeScript 2.1 (0ec0980)
- isolate: If you use JavaScript, this will not be a breaking change. If you use TypeScript 2.0, this is a
- isolate: as we are using exclusive TypeScript 2.1 features, only supported in v2.1.