Issues (9)

tests/unit/validations.test.js (5 issues)

1
import { inspect } from 'util';
2
import LIVR from 'livr';
3
import { assert,  AssertionError } from 'chai';
4
import { isFunction } from 'myrmidon';
5
import dayjs from 'dayjs';
6
import factory, { load } from '../Test';
7
8
load('lib/livr.js');
9
10
function testLIVR(data, rule, { valid, error } = {}) {
11
    try {
12
        const validator = new LIVR.Validator({ data: rule });
13
        const validData = validator.validate({ data });
14
        const errors = validator.getErrors();
15
16
        if (!error) {
17
            assert.notOk(errors, data);
18
            if (isFunction(valid)) return valid(validData.data);
0 ignored issues
show
Coding Style Best Practice introduced by
Curly braces around statements make for more readable code and help prevent bugs when you add further statements.

Consider adding curly braces around all statements when they are executed conditionally. This is optional if there is only one statement, but leaving them out can lead to unexpected behaviour if another statement is added later.

Consider:

if (a > 0)
    b = 42;

If you or someone else later decides to put another statement in, only the first statement will be executed.

if (a > 0)
    console.log("a > 0");
    b = 42;

In this case the statement b = 42 will always be executed, while the logging statement will be executed conditionally.

if (a > 0) {
    console.log("a > 0");
    b = 42;
}

ensures that the proper code will be executed conditionally no matter how many statements are added or removed.

Loading history...
19
            assert.ok(validData, data);
20
            assert.deepEqual(validData.data, valid);
21
        }
22
23
        if (error) {
0 ignored issues
show
Complexity Best Practice introduced by
There is no return statement if error is false. Are you sure this is correct? If so, consider adding return; explicitly.

This check looks for functions where a return statement is found in some execution paths, but not in all.

Consider this little piece of code

function isBig(a) {
    if (a > 5000) {
        return "yes";
    }
}

console.log(isBig(5001)); //returns yes
console.log(isBig(42)); //returns undefined

The function isBig will only return a specific value when its parameter is bigger than 5000. In any other case, it will implicitly return undefined.

This behaviour may not be what you had intended. In any case, you can add a return undefined to the other execution path to make the return value explicit.

Loading history...
24
            assert.ok(errors, data);
25
            assert.notOk(validData, data);
26
            assert.deepEqual(errors.data, error);
0 ignored issues
show
There is no return statement in this branch, but you do return something in other branches. Did you maybe miss it? If you do not want to return anything, consider adding return undefined; explicitly.
Loading history...
27
        }
28
    } catch (error_) {
29
        if (!(error_ instanceof AssertionError)) console.log(inspect(error_));
0 ignored issues
show
console.log looks like debug code. Are you sure you do not want to remove it?
Loading history...
Coding Style Best Practice introduced by
Curly braces around statements make for more readable code and help prevent bugs when you add further statements.

Consider adding curly braces around all statements when they are executed conditionally. This is optional if there is only one statement, but leaving them out can lead to unexpected behaviour if another statement is added later.

Consider:

if (a > 0)
    b = 42;

If you or someone else later decides to put another statement in, only the first statement will be executed.

if (a > 0)
    console.log("a > 0");
    b = 42;

In this case the statement b = 42 will always be executed, while the logging statement will be executed conditionally.

if (a > 0) {
    console.log("a > 0");
    b = 42;
}

ensures that the proper code will be executed conditionally no matter how many statements are added or removed.

Loading history...
30
        throw error_;
31
    }
32
}
33
34
suite('Utils: validators #no-pack');
35
36
before(async function () {
37
    await factory.cleanup();
38
});
39
40
test('Positive: Date', function () {
41
    [
42
        dayjs().toISOString(),
43
        dayjs(),
44
        dayjs().valueOf(),
45
        dayjs().toDate(),
46
        new Date()
47
    ].forEach(inp =>
48
        testLIVR(inp, 'date', { valid : out => {
49
            assert.equal(out.toISOString, dayjs(inp).toISOString);
50
        } }));
51
52
    [
53
        null,
54
        undefined,
55
        ''
56
    ].forEach(inp =>
57
        testLIVR(inp, 'date', { valid : out => {
58
            assert.equal(inp, out);
59
        } }));
60
});
61
62
test('Negative: Date', function () {
63
    [
64
        'date',
65
        '15.03',
66
        '26.05.2007'
67
    ].forEach(inp =>
68
        testLIVR(inp, 'date', { error: 'WRONG_DATE' }));
69
});
70