mapbox / mapbox/vector-tile-spec
Null values should be allowed
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1k
- Forks
- 213
- PR merge metrics
- No merged PRs in 30d
Description
2.1 specifies:
In order to support values of varying string, boolean, integer, and floating point types, the protobuf encoding of the value field consists of a set of optional fields. A value MUST contain exactly one of these optional fields.
The text "MUST contain exactly one" effectively prohibits null values. I think this was unintended, and the text should read "MUST contain either zero of these optional fields, in which case the value shall be interpreted as an untyped "null" value, or exactly one of them."
Contributor 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.
Research direction
Start with section 2.1 of the vector tile specification and locate the sentence requiring exactly one optional field. Update the wording to allow zero fields for an untyped null value while retaining the exactly-one rule for typed values; the section should clearly define both valid cases.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100