Łukasz Sentkiewicz
Łukasz Sentkiewicz
If you think there are core functions are missing, then I will be happy to accept PRs, but some functions from lodash/ramda are 1-liners. - `isNil`, I think it's not...
I am fine with `includes`, and `reverse` (`array.reverse()` mutates the array). `words`, and `unwords` are simple 1 liners, and they are not core functions. Can you explain `show`, `read`, `zip`,...
Would you be interested in creating a PR? `setPath` can work similarly to `pathOr`. We can't support string paths (`'a[0].b.c'`) because they are not typescript friendly.
Hi, Sorry for the delay. Would you be interested in submitting a PR?
Here is a pending PR https://github.com/remeda/remeda/pull/69
Only for pipe or for every function?
Does lodash or ramda have a similar function? What's an example use case for it?
Hi! You can always create your own wrapper. ```ts function typedModel( name: string, schema?: T, collection?: string, skipInit?: boolean ): Model { return db.model(name, schema, collection, skipInit) as any; }...
I am checking failed tests and this is confusing. Example failing test: ```js // jest/packages/expect/src/__tests__/to_throw_matchers.test.js test('passes', async () => { await jestExpect(asyncFn(false, true)).resolves.not[toThrow](); }); ``` `asyncFn(false, true)` resolves to `Promise.resolve('apple')`...
Does it make sense to split it to `rejects` and `resolves`? It would be enough to have only `promise` property. Examples ```js // new expect(value).promise.toEqual(expected); // old expect(value).resolves.toEqual(expected); // new...