Linting and formatting of exponent values do not agree with each other in pipeline nextflow schema vs json

[jfy133]

Description of the bug

We are trying to template merge 2.12 into nf-core/funcscan: https://github.com/nf-core/funcscan/actions/runs/7723141506/job/21052623682?pr=332

And we encounter a bunch of mismatches between exponent values between JSON schema and the nextflow config.

It appears that regardless of what you put in the 'nextflow_schema.json' schema, exponents are always formatted to 1e-09, whereas the nextflow config will always be 1E-9.

The only way we could get the linting to stop failing is to quote both, which is not ideal.

Command used and terminal output

No response

System information

No response

[jfy133]

It also appears that both linting forces large decimal 'numbers' to the different types of exponent

e.g. setting in funcscan in the nextflow.config

bgc_gecco_pfilter                       = 0.000000001

and in the nextflow_Schema.json

                "bgc_gecco_pfilter": {
                    "type": "number",
                    "description": "The p-value cutoff for protein domains to be included.",
                    "fa_icon": "fas fa-filter",
                    "default": 0.000000001,
                    "help_text": "The p-value cutoff for protein domains to be included.\n\nFor more information see the GECCO [documentation](https://github.com/zellerlab/GECCO).\n\n> Modifies tool parameter(s):\n> - GECCO: `--pfilter`"
                },

I still get the following linting error:

│ nextflow_config: Config default value incorrect: params.bgc_gecco_pfilter is set as 1e-09 in nextflow_schema.json but is 1E-9 in nextflow.config.          │

[mashehu]

fixed in #2712