Fixed FilteringTerm

was creating a FilteringTerm1 object
datsirul · Jul 25, 2024 · 4e4fd46 · 4e4fd46
1 parent 5a8c262
commit 4e4fd46
Showing 1 changed file with 12 additions and 12 deletions.
diff --git a/framework/src/responses/sections/beaconFilteringTermsResults.yaml b/framework/src/responses/sections/beaconFilteringTermsResults.yaml
@@ -10,9 +10,9 @@ properties:
   filteringTerms:
     type: array
     items:
-      $ref: '#/definitions/FilteringTerm'
+      $ref: '#/definitions/ResponseFilteringTerm'
 definitions:
-  FilteringTerm:
+  ResponseFilteringTerm:
     type: object
     description: >-
       Entities can be filtered using this term.
@@ -27,7 +27,7 @@ definitions:
           TODO: An ontology ... with a registered prefix does not need a full name
           so one may better use CURIE to indicate that the resource can be retrieved
           from the id. This also will allow to provide an enum here.
-        examples: 
+        examples:
           - "Human Phenotype Ontology"
           - alphanumeric
       id:
@@ -47,16 +47,16 @@ definitions:
           - 'B Lymphoblastic Leukemia/Lymphoma'
           - 'Aplasia/Hypoplasia of the middle ear'
       scopes:
-        description: >- 
+        description: >-
           Entry types affected by this filter.
-        examples: 
-          - 
-            - individual 
-            - biosample 
-            - analysis 
-            - run 
-            - genomicVariation 
-          - 
+        examples:
+          -
+            - individual
+            - biosample
+            - analysis
+            - run
+            - genomicVariation
+          -
             - biosample
         type: array
         items: