null stuff is about testing "validate ($.Undefined) (undefined) and make sure it succeeds.
I just notice that the last line in _test might create an infinite loop.
return x != null && t.keys.length > 0
? t.keys.map (k => _test (t.types[k]) (k) (t.extractors[k](x)[0]))
: _test (t) () (x);The false part of the ternary should never happen, I think...
null check here is because t.extractors[k] will crash if k is null.
// Maybe$1 :: Maybe a -> Array a
const Maybe$1 = S.maybe ([]) (a => [a]);// Either$1 :: Either a b -> Array a
const Either$1 = S.either (a => [a]) (b => []);
// Either$2 :: Either a b -> Array b
const Either$2 = S.either (a => []) (b => [b]);// Array$1 :: Array a -> Array a
const Array$1 = as => as;Array$1 returns all the elements of the array. ;)
var custom = util.inspect.custom; <-- TypeError: Cannot read properties of undefined (reading 'custom'). Do you know how to resolve this issue?My usage of Sanctuary looks like this
api.utils.js:import * as S from 'sanctuary'
export const processData = ({ data }) => S.pipe ([ S.head, S.props(['value', 'result']) ]) (data.rows)require:typeof module === 'object' && typeof module.exports === 'object'require ('util') will work in this context. This is not a safe assumption.
Symbol.for ('nodejs.util.inspect.custom'), obviating the need for require ('util'), circumventing this issue.
require ('util') from your end in the interim?
require ('util'), but I don't know how. For now I use downloaded bundle from CDN and did const S = window.sanctuary in utils file... I also tried using importmaps, but it looks like it interferes with Vite.
sanctuary-def and get type errors before pre-runtime (not sure if that's possible). Thanks!
@kee-oth, welcome to the community! :wave:
Awesome FP JS has a list of learning resources. I do not have a specific recommendation.
I'm not aware of any way to leverage sanctuary-def statically. That would be sweet!
// @ts-check in vscode. It will use the ts definition which is mostly correct. The definitions does not cover sanctuary 100% and will get confused sometimes and give you false errors. You can use the run-time type checking to check if they are really an error.
@kee-oth It helped me a lot to read https://mostly-adequate.gitbook.io/mostly-adequate-guide/ to learn about ADTs like Maybe and Either and how to un-nest types. But I would scan the examples as many of the later ones are broken. The concepts are correct but somehow over time the examples were updated to a state where they do not actually run as advertised. The maintainer says he does not have time to go through the examples at this time..
Other than that, me and two others bought https://leanpub.com/fp-made-easier... it does not have Sanctuary.js examples though but the most popular data types should work the same with either language/framework.
@kee-oth if you use vscode then turning on bracket pair colorization is a must :) https://code.visualstudio.com/updates/v1_60#_high-performance-bracket-pair-colorization
"editor.bracketPairColorization.enabled": true
1 reply