-
Notifications
You must be signed in to change notification settings - Fork 8
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.
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
extending data extraction endpoints with /contributions #34
Conversation
34bec81
to
03a1755
Compare
7e77331
to
1c5ef81
Compare
b8e622b
to
5b379b3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not done looking though the whole code yet, but I just realized one thing that I would really want to advice against: IMHO we should not add support for the old and deprecated types/keys/values parameters in this new endpoint is. Or is it unreasonably hard to drop the parameters for these resources?
src/main/java/org/heigit/ohsome/ohsomeapi/config/SwaggerConfig.java
Outdated
Show resolved
Hide resolved
I did not specifically add a support for it. So I'm just using the same framework that already exists in terms of parameter processing. What we could do is remove types/keys/values from the list of allowed parameters for this resource, so the user would get an error message when trying to use one of them in a request to /contributions |
sounds good 👍 . additionally, I'd say that in swagger and the documentation the parameters should not be suggested to the user if possible. |
I can remove them from swagger completely yes. The docs are another topic, which is actually still not existant for the /contributions endpoint. Need to add those still. |
6424701
to
969ad9f
Compare
def5ecc
to
7eb6060
Compare
to check if a proper empty geometry is returned
to incorporate the clipping flag
to handle creations, as they can also be included easier in the for-loop
to apply a better code flow
making DataRequestExecutor unstatic modifying javadoc comments accordingly
to keep a specific ordering of the sites through adding numbers in front
removing types, keys, values from list of valid params as they are deprecated
removing types, keys, values parameters from swagger
adding a new section for the new endpoint
adding http response status codes, solves #64
adapting their grouping modifying some descriptions
for HTTP status codes
This reverts commit 1d909b5.
for HTTP response codes
b08c398
to
d8f4c5f
Compare
This branch implements the first 2 points raised in issue #23, which are:
/contributions/geometry/
for the modifications as GeoJSON/contributions/latest/geometry/
for the "latest" changes only, as GeoJSONsame endpoints also for /bbox and /centroid respectively
add sphinx docs for the new endpoint + examples
For further rationale, please look at the discussions in PR #18.