Add byte array to Values message
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- backend-api-design
Research direction
Review the Values message definition and the decoder behavior described in the issue, then read the existing comment discussion before deciding whether a bytes value belongs in the specification. Done means reaching and documenting a decision on the eighth value type and how decoders should handle it.
Written by the indexing model from the issue text.
Description
We currently do not have a way to properly encode byte arrays as the value of an attribute. Ideally, this would not be an allowed type but I can see in some rare cases where this might be useful. I would like to propose adding bytes as the 8th value message and specifically state that it may be ignored in the decoder.
I know that from an data format standpoint that protobuffers do not have any difference between bytes and strings, however, I have come to realize that in some situations such as the python protobuf libraries it attempts to enforce a text encoding type on the values as they are set via the protobuf library. Additionally, it would be ideal for a client to know if there is a non standard string format that it could be ignored for situations where a bytes field is being used.
Thoughts?
/cc @ericfischer @joto
- Dominant language
- No language data
- Stars
- 1k
- Forks
- 213
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mapbox/vector-tile-spec
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
mapbox/vector-tile-spec#157 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
mapbox/vector-tile-spec#153 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
mapbox/vector-tile-spec#149 ·
-
Typo in §4.4Open
Difficulty 1/5 Under an hour Newbie friendliness 55/100
mapbox/vector-tile-spec#148 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
mapbox/vector-tile-spec#145 · 2 comments · 1 reaction ·
All issues in mapbox/vector-tile-spec
Similar issues
-
Warm-up comes out as one climb, or none, when the target is near the bottom of the board's gradesOpenbug epic:minimal-layout epic:workouts good first issue mobile priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ColeMurray/background-agents#2305 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oblien/openship#1086 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100