Skip to content
This repository has been archived by the owner on Aug 20, 2024. It is now read-only.

Releases: nextflow-io/nf-validation

Version 1.1.4 - Kushiro

07 Aug 15:51
750a56d
Compare
Choose a tag to compare
  • Ignore validation of Azure and GCP blob storage paths which caused false-negative errors (#171)

Version 1.1.3 - Asahikawa

21 Nov 10:34
26f5631
Compare
Choose a tag to compare

Improvements

  • Added support for double quotes (") in CSV and TSV samplesheets (#134)

Version 1.1.2 - Wakayama

16 Nov 12:24
975bc99
Compare
Choose a tag to compare

Bug fixes

  • Fixed an issue with inputs using file-path-pattern where only one file was found (Path casting to ArrayList error) (#132)

Version 1.1.1 - Shoyu

23 Oct 11:36
1a6bf69
Compare
Choose a tag to compare

Bug fixes

  • Fixed an issue where samplesheet with a lot of null values would take forever to validate (#120) => Thanks @awgymer for fixing this!
  • Now YAML files are actually validated instead of skipped (#124)

Version 1.1.0 - Miso

18 Oct 09:42
ac5812a
Compare
Choose a tag to compare

Features

  • Add support for samplesheets with no header (#115)

Bug fixes

  • Floats and doubles should now be created when using the number type in the schema (#113)
  • When 0 is used as a default value in the schema, a 0 will now be used as the value in the .fromSamplesheet() channel instead of null (#114)

New features

  • Added file-path-pattern format to check every file fetched using a glob pattern. Using a glob is now also possible in the samplesheet and will create a list of all files found using that glob pattern. (#118)

Version 1.0.0 - Tonkotsu

12 Oct 09:03
ffa4134
Compare
Choose a tag to compare

The nf-validation plugin is now in production use across many pipelines and has (we hope) now reached a point of relative stability. The bump to major version v1.0.0 signifies that it is suitable for use in production pipelines.

This version also introduces a small breaking change of syntax when providing optional arguments to the functions. You can now provide optional arguments such as the nextflow parameters schema path as:
validateParameters(parameters_schema: 'my_file.json')

(previous syntax used positional arguments instead).

Bug fixes

  • The path to a custom parameters schema must be provided through a map 'parameters_schema: 'my_file.json'' in validateParameters() and paramsSummaryMap() (#108)

Version 0.3.4

10 Oct 13:58
183247b
Compare
Choose a tag to compare

This version introduced a bug which made all pipeline runs using the function validateParameters() without providing any arguments fail.

This bug causes Nextflow to exit with an error on launch for most pipelines. It should not be used. It was removed from the Nextflow Plugin registry to avoid breaking people's runs.

Bug fixes

  • Do not check S3 URL paths with PathValidator FilePathValidator and DirectoryPathValidator (#106)
  • Make monochrome_logs an option in paramsSummaryLog(), paramsSummaryMap() and paramsHelp() instead of a global parameter (#101)

Version 0.3.3

10 Oct 10:36
3712e1d
Compare
Choose a tag to compare

Bug fixes

  • Do not check if S3 URL paths exists to avoid AWS errors, and add a new parameter validationS3PathCheck (#104)

Version 0.3.2

19 Sep 08:38
7ca22a4
Compare
Choose a tag to compare

Bug fixes

  • Add parameters defined on the top level of the schema and within the definitions section as expected params (#79)
  • Fix error when a parameter is not present in the schema and evaluates to false (#89)
  • Changed the schema_filename option of fromSamplesheet to parameters_schema to make this option more clear to the user (#91)

Version 0.3.1

12 Jul 09:10
700c919
Compare
Choose a tag to compare
Merge pull request #77 from mirpedrol/bump-0.3.1

bump to version 0.3.1