[QRQC_2] No explicit any in twenty-server (#12068)
# Introduction Added a no-explicit-any rule to the twenty-server, not applicable to tests and integration tests folder Related to https://github.com/twentyhq/core-team-issues/issues/975 Discussed with Charles ## In case of conflicts Until this is approved I won't rebased and handle conflict, just need to drop two latest commits and re run the scripts etc ## Legacy We decided not to handle the existing lint error occurrences and programmatically ignored them through a disable next line rule comment ## Open question We might wanna activate the [no-explicit-any](https://typescript-eslint.io/rules/no-explicit-any/) `ignoreRestArgs` for our use case ? ``` ignoreRestArgs?: boolean; ``` --------- Co-authored-by: etiennejouan <jouan.etienne@gmail.com>
This commit is contained in:
@ -27,6 +27,7 @@ export class SeederService {
|
||||
dataSourceId: string,
|
||||
workspaceId: string,
|
||||
objectMetadataSeed: ObjectMetadataSeed,
|
||||
// eslint-disable-next-line @typescript-eslint/no-explicit-any
|
||||
objectRecordSeeds: Record<string, any>[],
|
||||
): Promise<void> {
|
||||
const createdObjectMetadata = await this.objectMetadataService.createOne({
|
||||
@ -184,6 +185,7 @@ export class SeederService {
|
||||
private turnCompositeSubFieldValueAsSQLValue(
|
||||
fieldType: FieldMetadataType,
|
||||
subFieldName: string,
|
||||
// eslint-disable-next-line @typescript-eslint/no-explicit-any
|
||||
subFieldValue: any,
|
||||
) {
|
||||
if (!isCompositeFieldMetadataType(fieldType)) {
|
||||
@ -211,6 +213,7 @@ export class SeederService {
|
||||
|
||||
private turnFieldValueAsSQLValue(
|
||||
fieldType: FieldMetadataType,
|
||||
// eslint-disable-next-line @typescript-eslint/no-explicit-any
|
||||
fieldValue: any,
|
||||
) {
|
||||
if (fieldType === FieldMetadataType.RAW_JSON) {
|
||||
|
||||
Reference in New Issue
Block a user