v2.0.0

Changelog

• Added a distributed memory cache backend. We chose Memcached, thanks to @svenvc for porting the client to Pharo, and allowing us to collaborate on that project to release a v1 we can trust.
• Refactored some tests to improve code quality and fix listing issues.

Migration Guide

The version provides a package to perform an automatic migration. See the migration guide for further instructions.

v1.2.1

Changelog

• Fixed #31: Improving Expires error handling during parsing to be consistent with RFC 7234. Thanks @nchillo
• PR #29: Make RESTfulAPIClient>>#getAt:configuredBy:withSuccessfulResponseDo: part of the public API. Thanks @nchillo

v1.2.0

Changelog

• Core
  • Add setAuthorizationTo: to set Authotization headers in the builder
  • Add set:to: to set arbitrary headers in the builder
• API Client
  • Add postAt:configuredBy:withSuccessfulResponseDo: allowing better configuration of the request
  • Add APIClientTest to ease the testing of API Clients.
• Tooling
  • Add GitHub Actions to check the correct loading of every group declared in the Baseline

v1.1.0

Changelog

• Core
  • Refactor some internals of the request builder
  • HttpRequest now include methods to easily support DELETE, PATCH and PUT
  • HttpRequest instances can now be applied several times to the same HTTP Client
  • The header builder now supports setBearerTokenTo: , setIfMatchTo: and setIfNoneMatchTo:
• API Client
  • RESTfulAPIClient provides a building block to create more specific RESTful API clients by providing http clients pooling, automatic handling of ETag related headers, and by now in-memory caching
  • ExpiringCache provides an in-memory cache for incoming request responses adhering to the received caching directives
• Service Discovery
  • ConsulAgentHttpAPIBasedDiscoveryClient provides service discovery abilities using the Consul Health HTTP API as backend
  • FixedServiceDiscoveryClient provides basic service discovery abilities using a fixed list of services
  • All the service discovery clients can be used in a chained fashion
  • Add integration tests for the service discovery client using docker-compose
• Tooling
  • Use GitHub actions and CodeCov to run the build
  • Automatically send release announcements to the mailing list

Next steps

• Add usage documentation
• Provide some kind of caching policy so we can use different strategies according to the situation

v1.0.0

First version