Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

23019: add sortedByProximity parameter in locations.json #255

Merged
merged 1 commit into from
Dec 5, 2024
Merged

23019: add sortedByProximity parameter in locations.json #255

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
9 changes: 9 additions & 0 deletions docs/specs/tripgo.openapi.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2056,6 +2056,15 @@ paths:
schema:
type: boolean
default: false
- name: sortedByProximity
in: query
description: "If enabled the the results are sorted using the distance to the `center` as measure. Nearest results should be at the beginning of the list."
required: false
style: form
explode: true
schema:
type: boolean
default: false
responses:
"200":
description: Successful response
Expand Down
5 changes: 5 additions & 0 deletions docs/specs/tripgo.swagger.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1313,6 +1313,11 @@ paths:
type: boolean
description: Should "parent" public transport location (e.g., large station) include the details for each child stops (e.g., individual platforms)?
default: false
- name: sortedByProximity
in: query
type: boolean
description: If enabled the the results are sorted using the distance to the "center" as measure. Nearest results should be at the beginning of the list.
default: false
responses:
200:
description: Successful response
Expand Down