fluture-js / fluture-sanctuary-types Goto Github PK

exports.env = [
  FutureType($.Unknown, $.Unknown),
  ConcurrentFutureType($.Unknown, $.Unknown)
];

allowing for:

- $.create({checkTypes: true, env: $.env.concat([FutureType($.Unknown, $.Unknown), ConcurrentFutureType($.Unknown, $.Unknown)])})
+ $.create({checkTypes: true, env: $.env.concat(env)});

Version 1.5.0 of sanctuary-scripts was just published.

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

sanctuary-scripts 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.

Your Greenkeeper Bot 🌴

Hey there

I am wondering why my Fluture return value is not throwing for executeWrite but only as soon as we get to executeRead. How can I make it throw earlier?

TypeError: Invalid value

executeRead :: { path :: String } -> Future Any Buffer
                         ^^^^^^
                           1

My implementation:

const executeWrite_ = F.encaseP(({ path, contents }) =>
    fs.promises.writeFile(path, contents).then(() => 12) // PROVOKE TYPE VIOLATION
);

const executeWrite = def("executeWrite")({})([
    WriteOperationType,
    FlutureTypes.FutureType($.Any)($.String)
])(executeWrite_);

const executeRead_ = F.encaseP(({ path }) => fs.promises.readFile(path));

The test which writes a file and reads back from it.

test("write file e2e", t =>
    new Promise((resolve, reject) => {
        const fileName = "testFile";
        const contents =
            "contents " +
            Array.from({ length: 1 }, () => Math.random().toString(36)[2]).join(
                ""
            );
        const writeOp = executeWrite({ path: fileName, contents });
        const readOp = path => executeRead({ path });
        const readWrite = F.chain(readOp)(F.map(log("written"))(writeOp));
        const e2e = F.map(toString)(readWrite);
        F.fork(someError => reject(someError))(readContents => {
            log("resolve")(contents);
            t.equals(readContents, contents);
            resolve();
        })(e2e);
    }));

Thanks for the help 👋

The fluture-hooks library introduces the Hook and ConcurrentHook types.

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.

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.

Your Greenkeeper Bot 🌴

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

First off, thank you for creating these typings!

I'm completely new to Sancturary and Fluture and already I feel productive with Sanctuary's awesome type checking.

But after a lot of initial head scratching, since my requirements are bit odd (old).

I maintain a website that was build 6 years ago with jQuery, underscore.js and express, ejs on the server.

We do not have a built step for javascript (we do for CSS) and I had to figure out how to combine Sancturary + Fluture + jQuery in the browser. Luckily we only support ES2015, so modules are supported.

I came up with the following as a proof of concept:

<p id="output">Loading...</p>

<script>
	'use strict'
	const process = {}
	process.env = {}
	process.env.NODE_ENV = 'dev'
</script>
<script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/jquery.min.js" integrity="sha256-/xUj+3OJU5yExlq6GSYGSHk7tPXikynS7ogEvDej/m4=" crossorigin="anonymous"></script>
<script src="https://cdn.jsdelivr.net/gh/sanctuary-js/[email protected]/dist/bundle.js"></script>
<script type="module" src="js/app.js"></script>

js/app.js

import { env as flutureEnv } from './[email protected]'
import { Future, fork } from 'https://cdn.jsdelivr.net/gh/fluture-js/[email protected]/dist/module.js'


/** @type {import('sanctuary')} */
const S = window.sanctuary.create({ checkTypes: true, env: window.sanctuary.env.concat(flutureEnv) })

// getJSON :: String -> {} -> Task Error JN
const getJSON = S.curry2((url, params) => Future((reject, result) => {
	$.getJSON(url, params, result).fail(reject)

	// Here is how we handle cancellation. This signal is received when nobody
	// is interested in the answer any more.
	return function onCancel () {
		// Clearing the timeout releases the resources we were holding.
		console.log('Future was cancelled')
	}
}))

const display = S.pipe([
	S.prop('publishableKey'),
	key => $('#output').text(key)
])

fork (console.error) (display)
	(getJSON('/setup') ({}))

'./[email protected]' is my edited version of the current typings, since I can not use the implementation as it is.

The following changes was needed before I could get it to work:

const $D = window.sanctuaryDef
const type = window.sanctuaryTypeIdentifiers
import {
  Future,
  isFuture,
  extractLeft,
  extractRight,
  Par,
  seq
} from 'https://cdn.jsdelivr.net/gh/fluture-js/[email protected]/dist/module.js';

Contrast that with what is provided by fluture-sanctuary-types today:

import $ from 'sanctuary-def';
import type from 'sanctuary-type-identifiers';
import {
  Future,
  isFuture,
  extractLeft,
  extractRight,
  Par,
  seq
} from 'fluture/index.js';

Both app.js and [email protected] imports "https://cdn.jsdelivr.net/gh/fluture-js/[email protected]/dist/module.js" but it is only loaded by the browser once.
The process.env.NODE_ENV stuff is to turn Sanctuary type checking on/off.

Notice that $ had to be renamed to $D to not conflict with jQuery.

That was a lot of pretext.. What I wanted to ask is, is it possible to get a built hosted on jsDelivr that assumes Sancturary is global and imports Fluture from a CDN (preferably jsDelivr too)?
I'm not sure if depending on jsDelivr is the right path for everyone who needs to run Sanctuary + Fluture directly in the browser but it is an idea.

By the way, fluture-sanctuary-types works great with Fluture 14 in my very limited test. Currently npm will loudly protest if you try to use Fluture 14 because of the peer dependency semver requirement.

Hi ! Thanks a lot for this integration with Sanctuary, makes everything better 👍

I'm using typescript and have been working pretty well for Fluture and Sanctuary so far, however there are no @types/fluture-sanctuary-types library, with makes ts throw a Could not find a declaration file for module

i made a workaround by declaring the tipes in a file:

// ./src/misssingDeclarations/fluture-sanctuary-types.d.ts
declare module 'fluture-sanctuary-types' {
    export const env: ReadonlyArray<any>;
}

and

// tsconfig.json
{
  "compilerOptions": {
    "baseUrl": "./",
    "paths": {
      "fluture-sanctuary-types": [
        "./src/misssingDeclarations/fluture-sanctuary-types.d.ts"
      ]
    }, 
}

But seems there are no official typescript package.
Sorry for bothering let me know if there is any way i could contribute. 🙏

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.

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.

Your Greenkeeper Bot 🌴

Version 8.2.0 of sanctuary-type-classes was just published.

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

sanctuary-type-classes 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.

Your Greenkeeper Bot 🌴