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.

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

Use correct types in JSON #8

Open
highsource opened this issue Mar 2, 2016 · 1 comment
Open

Use correct types in JSON #8

highsource opened this issue Mar 2, 2016 · 1 comment
Labels

Comments

@highsource
Copy link
Collaborator

bezgl. Json output: es scheinen alle Felder als string codiert zu sein. Für manche Felder wäre vermutlich number das bessere Format.

http://data.deutschebahn.com/apis/fahrplan/#comment-2540192857

This concerns:

  • lat, lon, routeIdx, routeIdxFrom, routeIdxTo
  • priority?
  • id/stopid?
  • track? (not sure)
  • priority (in Notes)

These properties should have correct JSON types, not just strings.

@mRs-
Copy link

mRs- commented Sep 30, 2016

The main problem is, that the swagger files are obsolete then, I need to implement my own stuff now, because the swagger file is defined more but the API is returning everything as Stirngs :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants