Conflict no-useless-undefined with consistent-return

Thanks for all the eslint-plugin-unicorn checks! Very useful.

When I enable the eslint-plugin-unicorn/no-useless-undefined rule, and have consistent-return rule enabled too the following code gives one violation in the first rule. But if I change return undefined to return the later rule signals a violation. Maybe the no-useless-undefined rule is missing an option to skip this kind of code.

eslint-plugin-unicorn/no-useless-undefined

This simplified example removed the needed await calls present in the real code. Changing undefined to null trigger another violation. Well, I could disable the rule for this line, but there are many similar ones.

async compute(arg: number): Promise<number|undefined> {

    if(arg === 42) return undefined;
    return arg;
}

Thanks for looking mario

[crystalfp]

As I wrote, disabling the rule. Eslint should help developing clean code, but too many false positive, or unfixable issues do not help in this.

[fisker]

Your code seems not parse able, is it TypeScript? I think https://github.com/sindresorhus/eslint-plugin-unicorn/pull/1165 already fixed it, are you sure your version is v30?