Merge pull request #657 from cloudinary/fix/metadata-fields-api-response-types

Fix/metadata fields api response types

Author: cloudinary-pkoniu

types/cloudinary_ts_spec.ts

@@ -654,6 +654,9 @@ cloudinary.v2.api.add_metadata_field({
 
 cloudinary.v2.api.list_metadata_fields().then((result) => {
     console.log(result.metadata_fields[0].datasource);
+    console.log(result.metadata_fields[0].datasource.values[0].value);
+    console.log(result.metadata_fields[0].datasource.values[0].external_id);
+    console.log(result.metadata_fields[0].datasource.values[0].state);
 });
 
 cloudinary.v2.api.delete_metadata_field('EXTERNAL_ID_GET_LIST').then((res) => {

types/index.d.ts

@@ -702,7 +702,9 @@ declare module 'cloudinary' {
         mandatory: boolean;
         default_value: number;
         validation: object; //there are 4 types, we need to discuss documentation team about it before implementing.
-        datasource: DatasourceEntry;
+        datasource: {
+            values: Array<DatasourceEntry>
+        };
 
         [futureKey: string]: any;
     }
@@ -711,6 +713,12 @@ declare module 'cloudinary' {
         metadata_fields: MetadataFieldApiResponse[]
     }
 
+    export interface DatasourceEntry {
+        external_id?: string;
+        value: string;
+        state?: 'active' | 'inactive'
+    }
+
     export interface DatasourceChange {
         values: Array<DatasourceEntry>
     }
@@ -831,11 +839,6 @@ declare module 'cloudinary' {
 
     export type SignApiOptions = Record<string, any>;
 
-    export interface DatasourceEntry {
-        external_id?: string;
-        value: string;
-    }
-
     export namespace v2 {
 
         /****************************** Global Utils *************************************/