-
Notifications
You must be signed in to change notification settings - Fork 1
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
GetTraceData is accepting int instead of long? #2
Comments
@blackboxlogic any thoughts? I don't mind replacing the code from int to long but you might know something I don't...? |
I foresee problems if we use long and |
I see. Well, we'll need to do it in two steps - |
Confirmed in slack by someone that sounded confident: it's a long. If there are no traces with large IDs, then you don't need to change |
I'm noticing that element versions should also be
Maybe worth fixing at the same time. |
I've made OsmSharp/core#89 for the OsmSharp side of this. |
GetTraceData
is acceptingint
, shouldn't it acceptlong
like the rest of the API?The text was updated successfully, but these errors were encountered: