OAI / OAI/OpenAPI-Specification
Support for structured-headers de/serialization
Open
Nobody has claimed this yet.
headers
param serialization
- Dominant language
- Markdown
- Stars
- 31.2k
- Forks
- 9.2k
- Avg merge
- 6h 37m
- Merged PRs (30d)
- 27
Description
I expect
A way to express structured-fields serialization rfc8941
Here are some examples:
Example-IntegerHeader: 42
Example-BoolHdr: ?1
Example-StringHeader: "hello world"
Example-BinaryHdr: :cHJldGVuZCB0aGlzIGlzIGJpbmFyeSBjb250ZW50Lg==:
Example-StrListHeader: "foo", "bar", "It was the best of times."
Example-DictHeader: en="Applepie", da=*w4ZibGV0w6ZydGU=*
Note
In the near future, all http headers will probably be de/serialized using structured-header specs.
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
The issue names no repository files or tests. Start by reading RFC 8941 and the linked structured-fields specification, then use the listed integer, boolean, string, binary, list, and dictionary examples to understand the requested scope. Done means OpenAPI has an agreed, documented way to express structured-header serialization and deserialization.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100