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

Direction ID of type String fails parsing #2

Closed
stklcode opened this issue Nov 16, 2018 · 0 comments
Closed

Direction ID of type String fails parsing #2

stklcode opened this issue Nov 16, 2018 · 0 comments
Assignees
@stklcode
Labels
bug
Milestone
1.1.4

Comments

@stklcode
Copy link
Owner

Direction ID may be of type String in current ASEAG implementation, while still Integer in TFL version.

Make the mapping agnostic to also map Strings "1" or "2" correctly.
@stklcode stklcode self-assigned this Nov 16, 2018
@stklcode stklcode added the bug label Nov 16, 2018
@stklcode stklcode added this to the 1.1.4 milestone Nov 17, 2018
stklcode added a commit that referenced this issue Nov 17, 2018
@stklcode
Extend unit tests for accepted Non-Integer values (#2)
f0205d1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stklcode stklcode

Labels
bug
Projects
None yet
Milestone
1.1.4
Development

No branches or pull requests
1 participant
@stklcode