This repository has been archived by the owner on May 31, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since we are now supporting uin64 (or sth. like uint53^^) in the frontend, we can and should send the whole data to it.
I'm not 💯% sure, how the datasource is handled in the different use-cases, but I think it was already presented as a uint64 dataset there, and the conversion just happened in the single place changed in this PR. I'll double check this.The only place where uint64 was converted is the one in this change. In the datasource-properties the layer was already presented as uint64.
@fm3 @philippotto Would it be easy for you to test this change locally?