Describe the problem/error: If a metadata contains non-unique sample names in-addition to invalid instrument_platform values, "sample_name must be unique" error message is not returned to the user. Instead only error message about invalid instrument_platform is returned to the user.
Expected behaviour: "sample_name must be unique" error message should be returned to the user in-addition to other invalid errors
System Identification: DEV
Reproducible? Yes
If multiple areas are impacted list areas: Electron client 1.1.4 all platforms.
If compatibility/interoperability is impacted list products (e.g.): Gpas Portals.
illumina-fastq-upload_sample_name_same_invalid_platfrom.csv.zip
This is expected behaviour – schema selection is a necessary pre-validation step prior to the main, lazily evaluated validation process. However, I have made it trigger a ValidationError to avoid confusion.
Describe the problem/error: If a metadata contains non-unique sample names in-addition to invalid instrument_platform values, "sample_name must be unique" error message is not returned to the user. Instead only error message about invalid instrument_platform is returned to the user. Expected behaviour: "sample_name must be unique" error message should be returned to the user in-addition to other invalid errors
Steps to Reproduce:
System Identification: DEV Reproducible? Yes If multiple areas are impacted list areas: Electron client 1.1.4 all platforms. If compatibility/interoperability is impacted list products (e.g.): Gpas Portals. illumina-fastq-upload_sample_name_same_invalid_platfrom.csv.zip