Shouldn't it be a hard error? A warning would still allow for kicking off an expensive, time-consuming, and resource-heavy workflow that is being run with incorrect parameters.

For example, I changed params.str in the tutorial to params.greeting to avoid reserved words. However, I forgot to change my command from --str to --greeting.

That's not the result that I wanted. Parameter validation would have prevented this.

EDIT: It seems like part of the problem is that params can be used throughout the .nf script without first being registered. For example, I don't actually have to define a default value as params.greeting = 'Hello world!' because I can just reference the param directly:

"""
printf '${params.greeting}' | split -b 6 - chunk_
"""

That is to say, parameter validation requires parameter registration.

If this strict-mode functionality were to be introduced, it might have to be enabled in the config in order to avoid breaking changes.

Ideally, it would validate basic types (e.g. str, int, list of str), and maybe predefined values (e.g. params.env:str=['cpu','gpu'] or params.ram:int=range(4:16))

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.