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:
swift-http-structured-headers has been updated to [RFC
9651](https://www.ietf.org/rfc/rfc9651.html).
Modifications:
- Update documentation.
Result:
An up-to-date documentation.
Co-authored-by: Cory Benfield <lukasa@apple.com>
Motivation:
[RFC 9651](https://www.ietf.org/rfc/rfc9651.html) permits serializing an
integer in the range of -999,999,999,999,999 to 999,999,999,999,999
inclusive ([Section
4.1.4-2.1.1](https://www.ietf.org/rfc/rfc9651.html#section-4.1.4-2.1.1)).
As `RFC9651BareItem` takes values `integer` or `date` with an associated
value of type `Int`, that range is implicitly more constrained on 32-bit
platforms to a subset range of `Int32.min` to `Int32.max` inclusive.
Modifications:
- Adjust `RFC9651BareItem` to take values `integer` or `date` with an
associated value of type `Int64` instead, which is sufficient for the
permitted range.
Result:
Compatibility for the Integer and Date Structured Types on 32-bit
platforms.
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
Documentation is nice, and we can help support users by providing useful
clear docs.
Modifications
Add Docc to 5.6 and later builds
Make sure symbol references work
Add overview docs
Result
Nice rendering docs
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.