patrickmichalina / typescript-monads Goto Github PK

📚Write safer TypeScript using Maybe, List, Result, and Either monads.

License: MIT License

TypeScript 99.18% JavaScript 0.82%

typescript monads functional-programming immutability javascript node maybe-monad result-monad either-monad reader-monad

typescript-monads's Introduction

📚 typescript-monads

Better TypeScript Control Flow

typescript-monads helps you write safer code by using abstractions over messy control flow and state.

Installation

You can use this library in the browser, node, or a bundler

Node or as a module

npm install typescript-monads

Browser

<head>
 <script src="https://unpkg.com/typescript-monads"></script>
 <!-- or use a specific version to avoid a http redirect --> 
 <script src="https://unpkg.com/[email protected]/index.min.js"></script>
</head>

var someRemoteValue;
typescriptMonads.maybe(someRemoteValue).tapSome(console.log)

Example Usage

Maybe
List
Either
Reader
Result
State
Logger

Maybe

TODO

List

TODO

Either

TODO

Reader

TODO

Result

TODO

State

TODO

Logger

TODO

typescript-monads's People

Contributors

Stargazers

Watchers

Forkers

itryapitsin2 williamareynolds beachman4 flocasts parabolabam kaborso chrishadar porubenkoeugene dgtlmonk shanerogers no-turno peachest

typescript-monads's Issues

Maybe.toResult()

An in-range update of rollup is breaking the build 🚨

The devDependency rollup was updated from `0.67.3` to `0.67.4`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ build_test_release: * build - Failed

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Is Result, Either and Reader implemented?

It is not clear in the README if the Result, Either and Reader monad are implemented or not.
is it the monad that is "To do" or only the documentation?

I found in the source some file for Either and Reader, but none for Result.

AsyncMaybe

Property 'toResult' is missing in type 'IMaybe<T>' but required in type 'Maybe<T>'

When I use none function, it return a "IMaybe" interface instead of "Maybe", but there is no "toResult" in "IMaybe", so, it is not a "Maybe".

If I set 'strict' in tsconfig.json to 'false', errors gone.

So is it a bug?

src/domain/tree.ts:42:10 - error TS2741: Property 'toResult' is missing in type 'IMaybe<T>' but required in type 'Maybe<T>'.

42     else return none()
            ~~~~~~~~~~~~~

  node_modules/typescript-monads/maybe/maybe.d.ts:27:5
    27     toResult<E>(error: E): IResult<T, E>;
           ~~~~~~~~
    'toResult' is declared here.

An in-range update of rollup is breaking the build 🚨

The devDependency rollup was updated from `1.27.6` to `1.27.7`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

Release Notes for v1.27.7

2019-12-01

Bug Fixes

Fix a scenario where a reassignments to computed properties were not tracked (#3267)

Pull Requests

#3267: Fix incomplete computed property deoptimization (@lukastaegert)

Commits

The new version differs by 4 commits.

c753a7f 1.27.7
1b8a3de Update changelog
d5651be Fix incomplete computed property deoptimization (#3267)
d7e3993 Update changelog

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @types/jest is breaking the build 🚨

The devDependency @types/jest was updated from `24.0.13` to `24.0.14`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ build_test_release: * build - Failed

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from `10.12.11` to `10.12.12`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ build_test_release: * build - Failed

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from `11.12.1` to `11.12.2`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ build_test_release: * build - Failed

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

The devDependency rollup was updated from `1.9.2` to `1.9.3`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ build_test_release: * build - Failed

Release Notes for v1.9.3

2019-04-10

Bug Fixes

Simplify return expressions that are evaluated before the surrounding function is bound (#2803)

Pull Requests

#2803: Handle out-of-order binding of identifiers to improve tree-shaking (@lukastaegert)

Commits

The new version differs by 3 commits.

516a06d 1.9.3
a5526ea Update changelog
c3d73ff Handle out-of-order binding of identifiers to improve tree-shaking (#2803)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

The devDependency rollup was updated from `1.14.2` to `1.14.3`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ build_test_release: * build - Failed

Release Notes for v1.14.3

2019-06-06

Bug Fixes

Generate correct external imports when importing from a directory that would be above the root of the current working directory (#2902)

Pull Requests

#2902: Use browser relative path algorithm for chunks (@lukastaegert)

Commits

The new version differs by 4 commits.

c68bd95 1.14.3
d79aa57 Update changelog
7179390 Use browser relative path algorithm for chunks (#2902)
b1df517 Add funding button

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of uglify-js is breaking the build 🚨

The devDependency uglify-js was updated from `3.5.2` to `3.5.3`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

uglify-js is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ build_test_release: * build - Failed

Release Notes for v3.5.3

Commits

The new version differs by 3 commits.

fa43768 v3.5.3
a74e600 mangle shadowed lambda under ie8 correctly (#3356)
4b21526 Fix test expectation (#3357)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

AsncResult

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from `12.12.15` to `12.12.16`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ ci/circleci: build: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Documentation

Add reducer funcationality to `Result`

Rather frequently, I'm collapsing collections of Result and needing a way to easily collapse values together in Ok, or toggle the Result to Fail if it exists. Using Rust as an example, there's a good abstraction with having the and and or functions built into the result class to allow for this behavior (reference to Boolean Operators in https://doc.rust-lang.org/std/result/).

I'd like to request this type reducer functionality be added to the Result type.

Break out each into own package/sub-directory?

An in-range update of semantic-release is breaking the build 🚨

The devDependency semantic-release was updated from `15.12.3` to `15.12.4`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ build_test_release: * build - Failed

Release Notes for v15.12.4

15.12.4 (2018-11-30)

Bug Fixes

remove unnecessary branch parameter from push function (ffe1062)

Commits

The new version differs by 1 commits.

ffe1062 fix: remove unnecessary branch parameter from push function

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from `11.11.3` to `11.11.4`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ build_test_release: * build - Failed

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Rewrite lib using classes.

Results in a memory improvement using prototypes via es6 classes when large number of objects are instantiated.
Maintain the same API for instantiating new objects. IE, do not require the use of new Maybe() but instead use maybe().
1 level of inheritance from type monad an option.

An in-range update of ts-jest is breaking the build 🚨

The devDependency ts-jest was updated from `24.0.0` to `24.0.1`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ts-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ build_test_release: * build - Failed

Commits

The new version differs by 23 commits.

b43b3c1 chore(release): 24.0.1
2d91a37 chore: update package-lock
485d3f7 build(deps): bump semver from 5.6.0 to 5.7.0 (#1043)
2bd2534 build(deps-dev): bump @types/node from 10.14.3 to 10.14.4 (#1041)
bdba560 build(deps-dev): bump @types/node from 10.14.2 to 10.14.3 (#1038)
08766bf build(deps-dev): bump @types/node from 10.14.1 to 10.14.2 (#1036)
5f92fd2 build(deps-dev): bump js-yaml from 3.12.2 to 3.13.0 (#1034)
a9c79e9 build(deps-dev): bump @types/yargs from 12.0.9 to 12.0.10 (#1032)
245ab29 build(deps-dev): bump eslint from 5.15.2 to 5.15.3 (#1031)
4e72e59 build(deps-dev): bump eslint from 5.15.1 to 5.15.2 (#1030)
fb7dd55 feat(config): specify package.json location (#823) (#1013)
279edcd build(deps-dev): bump tslint from 5.13.1 to 5.14.0 (#1028)
8b93228 build(deps-dev): bump @types/node from 10.12.30 to 10.14.1 (#1027)
b825c7f build(deps-dev): bump @types/lodash.memoize from 4.1.4 to 4.1.6 (#1014)
6f0ab80 build(deps-dev): bump @types/lodash.merge from 4.6.5 to 4.6.6 (#1015)

There are 23 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from `11.13.7` to `11.13.8`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ build_test_release: * build - Failed

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

The automated release is failing 🚨

🚨 The automated release from the `master` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Missing `package.json` file.

A package.json file at the root of your project is required to release on npm.

Please follow the npm guideline to create a valid package.json file.

Good luck with your project ✨

Your semantic-release bot 📦🚀

An in-range update of @types/jest is breaking the build 🚨

The devDependency @types/jest was updated from `23.3.9` to `23.3.10`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ build_test_release: * build - Failed

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from `10.12.7` to `10.12.8`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ build_test_release: * build - Failed

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

The devDependency rollup was updated from `1.18.0` to `1.19.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ build_test_release: * build - Failed

Commits

The new version differs by 6 commits.

9af119d 1.19.0
b3f361c Update changelog
456f4d2 Avoid variable from empty module name be empty (#3026)
17eaa43 Use id of last module in chunk as name base for auto-generated chunks (#3025)
871bfa0 Switch to a code-splitting build and update dependencies (#3020)
2443783 Unified file emission api (#2999)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

patrickmichalina / typescript-monads Goto Github PK

typescript-monads's Introduction

📚 typescript-monads

Better TypeScript Control Flow

Installation

Node or as a module

Browser

Example Usage

Maybe

List

Either

Reader

Result

State

Logger

typescript-monads's People

Contributors

Stargazers

Watchers

Forkers

typescript-monads's Issues

The devDependency rollup was updated from 0.67.3 to 0.67.4.

The devDependency rollup was updated from 1.27.6 to 1.27.7.

Bug Fixes

Pull Requests

The devDependency @types/jest was updated from 24.0.13 to 24.0.14.

The devDependency @types/node was updated from 10.12.11 to 10.12.12.

The devDependency @types/node was updated from 11.12.1 to 11.12.2.

The devDependency rollup was updated from 1.9.2 to 1.9.3.

Bug Fixes

Pull Requests

The devDependency rollup was updated from 1.14.2 to 1.14.3.

Bug Fixes

Pull Requests

The devDependency uglify-js was updated from 3.5.2 to 3.5.3.

The devDependency @types/node was updated from 12.12.15 to 12.12.16.

The devDependency semantic-release was updated from 15.12.3 to 15.12.4.

15.12.4 (2018-11-30)

Bug Fixes

The devDependency @types/node was updated from 11.11.3 to 11.11.4.

The devDependency ts-jest was updated from 24.0.0 to 24.0.1.

The devDependency @types/node was updated from 11.13.7 to 11.13.8.

🚨 The automated release from the master branch failed. 🚨

Missing package.json file.

The devDependency @types/jest was updated from 23.3.9 to 23.3.10.

The devDependency @types/node was updated from 10.12.7 to 10.12.8.

The devDependency rollup was updated from 1.18.0 to 1.19.0.

Recommend Projects

Recommend Topics

Recommend Org

The devDependency rollup was updated from `0.67.3` to `0.67.4`.

The devDependency rollup was updated from `1.27.6` to `1.27.7`.

The devDependency @types/jest was updated from `24.0.13` to `24.0.14`.

The devDependency @types/node was updated from `10.12.11` to `10.12.12`.

The devDependency @types/node was updated from `11.12.1` to `11.12.2`.

The devDependency rollup was updated from `1.9.2` to `1.9.3`.

The devDependency rollup was updated from `1.14.2` to `1.14.3`.

The devDependency uglify-js was updated from `3.5.2` to `3.5.3`.

The devDependency @types/node was updated from `12.12.15` to `12.12.16`.

The devDependency semantic-release was updated from `15.12.3` to `15.12.4`.

The devDependency @types/node was updated from `11.11.3` to `11.11.4`.

The devDependency ts-jest was updated from `24.0.0` to `24.0.1`.

The devDependency @types/node was updated from `11.13.7` to `11.13.8`.

🚨 The automated release from the `master` branch failed. 🚨

Missing `package.json` file.

The devDependency @types/jest was updated from `23.3.9` to `23.3.10`.

The devDependency @types/node was updated from `10.12.7` to `10.12.8`.

The devDependency rollup was updated from `1.18.0` to `1.19.0`.