Motivation:
Swift 6.0 is no longer supported, we should bump the tools version and
remove it from our CI.
Modifications:
* Bump the Swift tools version to Swift 6.1
* Remove Swift 6.0 jobs where appropriate in main.yml, pull_request.yml
Result:
Code reflects our support window.
Motivation:
The parser and serializer for the Display String type have been
implemented. The high-level encoder and decoder should follow.
Modifications:
Implement the encoder and decoder for Display String.
Result:
The StructuredFieldValues module will support the Display String type.
---------
Co-authored-by: Cory Benfield <lukasa@apple.com>
Motivation:
The parser and serializer for the Date type has been implemented. The high-level encoder and decoder should follow.
Modifications:
- Implement the encoder and decoder for Date.
Result:
The StructuredFieldValues module will support the Date type.
Migrate CI to use GitHub Actions.
Motivation:
To migrate to GitHub actions and centralised infrastructure.
Modifications:
Changes of note:
* Adopt swift-format using rules from SwiftNIO
* Remove scripts and docker files which are no longer needed
Result:
Feature parity with old CI.
Motivation:
`swift-http-structured-headers` has to be updated to [RFC 9651](https://www.ietf.org/rfc/rfc9651.html). And it will be convenient for users to have this update as a SemVer minor.
Modifications:
- Deprecate the `BareItem` type and replace it with `RFC9651BareItem`, retaining existing behaviours. Updates for the new RFC will be based on `RFC9651BareItem`.
Result:
The library can be updated to the new RFC in a backward-compatible manner.
* Remove Swift 5.5 Dockerfile
Motivation:
Swift 5.5 is no longer supported.
Modifications:
Remove Swift 5.5 Dockerfile
Result:
Swift 5.5 support fully removed
* Remove SHSendable
---------
Co-authored-by: Cory Benfield <lukasa@apple.com>
Motivation:
In general we should try to be specific about what we're referring to.
"Structured headers" is not really an accurate description of what this
module works with: "Structured Header Field Values", or "Structured
Field Value" is usually better. To that end this change adjusts our
naming to be closer to what we want. It also changes our module names to
prioritise the use of the Codable-based one.
Modifications:
- Renamed CodableStructuredHeaders to StructuredFieldValues.
- Renamed StructuredHeaders to RawStructuredFieldValues.
- Renamed a number of types from Field to FieldValue.
- Renamed a number of types from Header to Field or FieldValue.
- Renamed some functions along the above lines.
Result:
Better and more consistent terminology will be used.