push.rocks/smartrx
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(ci): Update CI workflows, dependency versions, and TypeScript configuration

Browse Source
This commit is contained in:
Philipp Kunz
2025-04-25 09:01:40 +00:00
parent e0a4e5a076
commit 5e16294773
12 changed files with 2249 additions and 1085 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
readme.md
View File

@@ -16,7 +16,7 @@ This package is distributed via npm and should be saved as a dependency in your
`@push.rocks/smartrx` provides a smart wrapper for working with RxJS, enhancing its already powerful reactive programming capabilities with additional functionalities, including easier observable map management and observable intake handling. We'll explore key features and how to use them in TypeScript.
First, ensure you're working in an environment configured for TypeScript and modern JavaScript development.
First, ensure you're working in an environment configured for TypeScript and modern JavaScript development.
### Basic Setup
@@ -84,7 +84,6 @@ observableIntake.signalComplete();
`ObservableIntake` offers the flexibility of adding values as they come and controlling when those values are emitted to subscribers, including buffering capabilities for managing backpressure.
#### Advanced Use-cases
`@push.rocks/smartrx` is built to handle more sophisticated scenarios like working with streams or handling events in a web environment.
@@ -102,7 +101,7 @@ Remember, reactive programming with RxJS is a powerful paradigm that can make ha
## License and Legal Information
This repository contains open-source code that is licensed under the MIT License. A copy of the MIT License can be found in the [license](license) file within this repository.
This repository contains open-source code that is licensed under the MIT License. A copy of the MIT License can be found in the [license](license) file within this repository.
**Please note:** The MIT License does not grant permission to use the trade names, trademarks, service marks, or product names of the project, except as required for reasonable and customary use in describing the origin of the work and reproducing the content of the NOTICE file.