Azure / Azure/azure-functions-host
Protobuf contract must not contain map<string, string> types
- Dominant language
- C#
- Stars
- 2k
- Forks
- 482
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 38
Description
In our protobuf contract, "map" type values should never be a native type (if it can be a null value), because it causes a Buffer overrun in JavaScript (and other languages).
https://github.com/Azure/azure-functions-language-worker-protobuf/issues/21
This issue is to track a potential major version change in the protobuf contract to change all map to map (or other nullable type
cc: @pragnagopa
Contributor guide
Research direction
Start by reviewing the protobuf contract and the linked Azure Functions language worker issue to identify every map value that can be null. A complete change would use a nullable value type throughout the contract and account for the required major version change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100