Xavier Garcia Buils

Inconsistent behaviour in empty method.

1

I read about this test and don't understand why exist. ``` it('should ignore invalid arguments safely', function(){ var obj = {}; // 1 expect(objectPath.empty()).to.equal(void 0); // 2 expect(objectPath.empty(obj, 'path')).to.equal(void 0);...

Is really necessary specify "No parts of <...> value should be checked"?

11

Hi! After reading #210, I still don't understand why these kind of law are needed. The topic starts talking about "No parts of `b` return value should be checked. But,...

chain default function implementation (analysis & maybe a simplification)

1

We have the following function in [source/chain.js](https://github.com/ramda/ramda/blob/960cc98e81c72faf812304d010675e0814b9a276/source/chain.js) implementation: ``` javascript function chain(fn, monad) { if (typeof monad === 'function') { return function(x) { return fn(monad(x))(x); }; } return _makeFlat(false)(map(fn, monad));...

Example: We have a reduceBy function where: * key function returns 'even' if the input is even, 'odd' id the input is odd and 'NaN' if the input is not...

Keep symmetric behaviour when composing or using transducers with arrays and objects

2

We have this code: ``` javascript var mapSquare = R.map(x => x * x); var mapInc = R.map(R.inc); var intoArray = R.into([]); var intoObject = R.into({}); var fn = R.compose(mapSquare,...

Hi! After investigating a little bit about how to bring [support to gherkin 6](https://github.com/vsiakka/gherkin-lint/issues/187), I found that the new parser version does not export [DIALECTS](https://github.com/vsiakka/gherkin-lint/blob/54ee5565fd7009ad7b03f83b560d76ceb2c66fcd/src/rules/indentation.js#L2) property. If we don't have...

no-unused-variables is also checking undeclared variables.

3

After looking into this code: ``` javascript for (const variable in examplesVariables) { if (!scenarioVariables[variable]) { errors.push({ message: `Examples table variable "${variable}" is not used in any step`, rule: rule,...

Nowadays when you write a Background after a Scenario is failing the `up-to-one-background-per-file` rule. Example: ``` gherkin @featuretag @featuretag1 @anothertag Feature: Feature with multiple duplicate tags @scenariotag @scenariotag1 Scenario Outline:...

In the same way that ``` gherkin @tag1 Feature: Feature with superfluous tags @tag1 Scenario: This is a Scenario name Then this is a then step Scenario: This is another...

Given a file tree: ``` + one + one.feature + two + two.feature ``` and gherkin-lintignore: ``` o*e ``` files in `one/` are not ignored. Notice that `eslint` with `.eslintignore`...