Last month, swift-http-types 0.1.0 became open source and we received a lot of great feedbacks from the community. We hope to take the next step to deliver a stable release in September.
Currently, this is the list of outstanding issues that we plan to resolve before 1.0:
- Should order matter when comparing HTTPFields for equality? #6
- More consistent naming for HTTPFields subscripts #9
- Missing built-in field names #12
- Support Codable #13
Please let us know what you think by replying below or filing new issues: Issues · apple/swift-http-types · GitHub