Skip to content
This repository has been archived by the owner on Oct 23, 2023. It is now read-only.

Allow implicit and explicit varianttype for mate #87

Merged
merged 1 commit into from
Apr 26, 2019
Merged

Allow implicit and explicit varianttype for mate #87

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 24 additions & 2 deletions beacon_api/schemas/query.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,7 +107,12 @@
"oneOf": [{
"required": [
"variantType"
]
],
"not": {
"required": [
"mateName"
]
}
},
{
"required": [
Expand All @@ -117,7 +122,24 @@
{
"required": [
"mateName"
]
],
"not": {
"required": [
"variantType"
]
}
},
{
"required": [
"mateName",
"variantType"
],
"properties": {
"variantType": {
"type": "string",
"enum": ["BND"]
}
}
}
]
}, {
Expand Down
4 changes: 4 additions & 0 deletions docs/optionals.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -106,6 +106,10 @@ Currently querying for a ``BND`` using ``startMin``, ``startMax`` and ``endMin``
with ``variantType=BND`` has the response illustrated below.
Fixed ``start`` and ``end`` can be utilised, as well as ``mateName`` as depicted above.

.. note:: By default when using ``mateName``, ``variantType`` is implicit ``BND``,
but it can also be set in an explicit manner using both ``mateName`` and
``variantType=BND`` in a query.

.. code-block:: javascript

{
Expand Down