Anıl Anar
Anıl Anar
@RobRukavina An idea: For `global.IS_REACT_ACT_ENVIRONMENT = false;`, it can be a `beforeAll` ordering issue. Testing library uses `beforeAll` too so you need to make sure your `beforeAll` runs after testing...
@Lokua Because you are not supposed to use `act` when `IS_REACT_ACT_ENVIRONMENT` is falsy. That warning is logged when you use `act` and react detects that `IS_REACT_ACT_ENVIRONMENT` is not true.
@ajselvig Considering these routing templates are called `path-to-regexp` strings, isn't https://github.com/pillarjs/path-to-regexp what you are looking for? It basically takes a string template and produces a regexp with which you can...
There's one catch to this proposal: wrapping an `import` is not valid ES6 and will cause babel to complain as such: `'import' and 'export' may only appear at the top...
+1, it can be an option like `limit_per_group: true/false`.
@TylorS I couldn't make that work with `typescript@next` (4.1.0.dev.blabla). e.g. ```typescript const array: Functor = { map: (f, F) => F.map(f), }; ``` complains `Type 'B' is not assignable to...
Maybe you can deprecate your library as this issue is still open since 2015.
Wouldn't it be better to use a tagged union type for errors instead of using prototype inheritence?
@PunGy That's true in Javascript (and possibly also Typescript) but perhaps not in "fp-ts" ecosystem simply because pattern matching on the error type can never be exhaustive because the type...