Skip to content

Commit

Permalink
Merge pull request #82 from ga4gh-beacon/schema-urgent-fixes
Browse files Browse the repository at this point in the history
missing object type fix
  • Loading branch information
costero-e authored Jul 16, 2024
2 parents ae4214a + 731de0e commit de014e8
Show file tree
Hide file tree
Showing 13 changed files with 46 additions and 340 deletions.
3 changes: 2 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
### Fixed

* Fixed `POST`queries for `g_variant` (w/ examples)
* Removed 'json' references inside the yaml version (PR [#43] (https://github.com/ga4gh-beacon/beacon-v2/pull/43))
* Removed 'json' references inside the yaml version (PR [#43](https://github.com/ga4gh-beacon/beacon-v2/pull/43))
* added missing `type: object` to `ResultsetInstance` (PR [#82](https://github.com/ga4gh-beacon/beacon-v2/pull/82))

### Deprecated

Expand Down
17 changes: 10 additions & 7 deletions framework/json/common/beaconCommonComponents.json
Original file line number Diff line number Diff line change
Expand Up @@ -76,11 +76,10 @@
},
"Granularity": {
"default": "boolean",
"description": "Level of detail of the response:\n* `boolean`: returns true/false' responses * `count`: adds the total number of positive results found * `aggregated`: returns summary, aggregated or distribution like responses * `record`: returns details for every row. In cases where a Beacon prefers to return records with fewer than allattributes, different strategies have to be considered w/o adding them to the current design, e.g.:\n - keeping non-mandatory attributes empty\n - Beacon to provide a minimal record definition",
"description": "Level of detail of the response:\n* `boolean`: returns true/false' responses * `count`: adds the total number of positive results found * `record`: returns details for every row. In cases where a Beacon prefers to return records with fewer than allattributes, different strategies have to be considered w/o adding them to the current design, e.g.:\n - keeping non-mandatory attributes empty\n - Beacon to provide a minimal record definition",
"enum": [
"boolean",
"count",
"aggregated",
"record"
],
"type": "string"
Expand Down Expand Up @@ -111,15 +110,19 @@
},
"HandoverType": {
"$ref": "./ontologyTerm.json",
"description": "Handover type, as an Ontology_term object with CURIE syntax for the `id` value. Use `CUSTOM` for the `id` when no ontology is available.",
"description": "Handover type, as an Ontology_term object with CURIE syntax for the `id` value. Use \"CUSTOM:123455\" CURIE-style `id` when no ontology is available.",
"examples": [
{
"id": "EFO:0004157",
"label": "BAM format"
"id": "EDAM:2572",
"label": "BAM"
},
{
"id": "CUSTOM",
"label": "download genomic variants in .pgxseg file format"
"id": "EDAM:3016",
"label": "VCF"
},
{
"id": "CUSTOM:pgxseg",
"label": "genomic variants in .pgxseg file format"
}
]
},
Expand Down
54 changes: 0 additions & 54 deletions framework/json/common/validation/beaconCommonComponents.json

This file was deleted.

109 changes: 0 additions & 109 deletions framework/json/requests/validation/filteringTerms.json

This file was deleted.

3 changes: 2 additions & 1 deletion framework/json/responses/sections/beaconResultsets.json
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,8 @@
"exists",
"resultsCount",
"results"
]
],
"type": "object"
}
},
"description": "Sets of results to be returned as query response.",
Expand Down
16 changes: 8 additions & 8 deletions framework/src/common/beaconCommonComponents.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -137,7 +137,6 @@ definitions:
* `boolean`: returns true/false' responses
* `count`: adds the total number of positive results found
* `aggregated`: returns summary, aggregated or distribution like responses
* `record`: returns details for every row. In cases where a Beacon prefers
to return records with fewer than allattributes, different strategies have
to be considered w/o adding them to the current design, e.g.:
Expand All @@ -147,7 +146,6 @@ definitions:
enum:
- boolean
- count
- aggregated
- record
default: boolean
TestMode:
Expand Down Expand Up @@ -265,11 +263,13 @@ definitions:
example: https://api.mygenomeservice.org/Handover/9dcc48d7-fc88-11e8-9110-b0c592dbf8c0/
HandoverType:
description: >-
Handover type, as an Ontology_term object with CURIE syntax for the `id` value.
Use `CUSTOM` for the `id` when no ontology is available.
Handover type, as an Ontology_term object with CURIE syntax for the `id`
value. Use "CUSTOM:123455" CURIE-style `id` when no ontology is available.
$ref: ./ontologyTerm.yaml
examples:
- id: EFO:0004157
label: BAM format
- id: CUSTOM
label: download genomic variants in .pgxseg file format
- id: EDAM:2572
label: BAM
- id: EDAM:3016
label: VCF
- id: CUSTOM:pgxseg
label: genomic variants in .pgxseg file format
37 changes: 0 additions & 37 deletions framework/src/common/validation/beaconCommonComponents.yaml

This file was deleted.

88 changes: 0 additions & 88 deletions framework/src/requests/validation/filteringTerms.yaml

This file was deleted.

1 change: 1 addition & 0 deletions framework/src/responses/sections/beaconResultsets.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ required:
additionalProperties: true
definitions:
ResultsetInstance:
type: object
properties:
id:
description: id of the resultset
Expand Down
Loading

0 comments on commit de014e8

Please sign in to comment.