HubSpot.Api 9.0.3

• net10.0

  • Microsoft.Extensions.Logging.Abstractions (>= 10.0.12)
  • Refit (>= 15.2.0)

Breaking change: query filters are now request objects, and CancellationToken is mandatory.

     The major version stays at 9 because it tracks the version of the HubSpot API this library
     targets, not the shape of the library's own surface. Read the version number as "HubSpot API
     v9"; it does not follow semantic versioning, so a major version that has not moved is not a
     promise that your code still compiles. This release will not compile against existing calls.

     Endpoints that took a list of optional query parameters now take one request object:

       Before: GetPageAsync(limit: 10, properties: ["name"], cancellationToken: ct)
       After:  GetPageAsync(new CrmPageRequest { Limit = 10, Properties = ["name"] }, ct)

       Before: GetAsync(id, properties: ["name"], cancellationToken: ct)
       After:  GetAsync(id, new CrmGetRequest { Properties = ["name"] }, ct)

     CrmPageRequest derives from CrmGetRequest, adding Limit and After, so a caller that already
     has filters for one endpoint can reuse them across object types. IDomains.GetPageAsync takes
     DomainPageRequest. Where no filters are wanted, pass new().

     Every CancellationToken parameter has lost its "= default" and is now required. Calls that
     relied on the default will no longer compile; pass the token explicitly. Calls that passed it
     by name (cancellationToken: ct) still compile once the new request argument is supplied.

     The query string sent to HubSpot is unchanged: each request property carries an explicit
     AliasAs, and the outgoing URI is now covered by tests that need no portal credentials.

     Motivation: the optional parameters drew 92 static analysis findings, and the six-parameter
     filter block repeated across nine interfaces was the bulk of the library's reported code
     duplication. Both are resolved by the single shared request type.