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

Jump to bottom

API is not clear #5

Open
bleucitron opened this issue Apr 22, 2018 · 0 comments
Open

API is not clear #5

bleucitron opened this issue Apr 22, 2018 · 0 comments

Comments

@bleucitron
Copy link

bleucitron commented Apr 22, 2018 •
edited
Loading

The API as described in the docs could use some clarity.

Some methods (removeTrailingSlashes, simpleObjectDeepClone,...) are clearly utils and could be stored under utils.

"Request" methods (not the OsmRequest instance) are not coherent.
The write methods require an instance of osm-auth, but no endpoint is required (unlike fetch methods). How do you then point to the osm dev instance with write method ?

Maybe clarify the docs ?
PanierAvide pushed a commit that referenced this issue May 19, 2019
@ThomasG77
Get full related elements from way or relations v2 (#5)
24bea33 
* Get full related elements from way or relations v2

* Solve missing option description
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bleucitron