Closed demariadaniel closed 3 months ago
some of the stringifiedRecords
in this codebase is actually stringified and some is not.
sometimes a TypedDataRecord
is the type other times it's DataRecord
export declare class DataRecord {
readonly [k: string]: string | string[];
}
export declare class TypedDataRecord {
readonly [k: string]: SchemaTypes;
}
``` from lectern client schema entities
some of the
stringifiedRecords
in this codebase is actually stringified and some is not. sometimes aTypedDataRecord
is the type other times it'sDataRecord
export declare class DataRecord { readonly [k: string]: string | string[]; } export declare class TypedDataRecord { readonly [k: string]: SchemaTypes; } ``` from lectern client schema entities
I will double check this is all being handled properly. This is because revalidating records and checking for exceptions need similar (but not equal) record values and use of any
elsewhere is obscuring potential issues
Link to Issue
https://github.com/icgc-argo/argo-clinical/issues/1146
Description
ClinicalErrors / Submitted Data page fail when requested migration dictionary cannot be found
Updates schemaRepo.get to allow direct request for specific dictionary version
Refactors
getValidRecordsPostSubmission
, renamed tofilterErrorsWithUpdatesOrExceptions
If
filterErrorsWithUpdatesOrExceptions
cannot find the required Dictionary, it makes a request to Lectern and saves the needed Dictionary to the DBFixes
matchDonorErrorsWithExceptions
bug which created duplicate error recordsOverall code readability improvements
Checklist
Type of Change
Checklist before requesting review:
develop
not master)validationDependency
in meta tag for Argo Dictionary fields used in code