Use Refit for HTTP calls

[Copilot]

Replaced manual HttpClient calls with Refit, a type-safe REST client library.

Changes

Added Dependencies

• Refit 7.2.22
• Refit.HttpClientFactory 7.2.22

Implementation

• Created resource-specific Refit interfaces for each WordPress REST API endpoint:

  • IPostsApi - Posts endpoint with CRUD operations
  • IPagesApi - Pages endpoint with CRUD operations
  • ICommentsApi - Comments endpoint with CRUD operations
  • ITagsApi - Tags taxonomy endpoint
  • ICategoriesApi - Categories taxonomy endpoint
  • IUsersApi - Users endpoint including current user
  • IMediaApi - Media/attachments endpoint
  • ITaxonomiesApi - Custom taxonomies endpoint
  • IPostTypesApi - Post types metadata endpoint
  • IPostStatusesApi - Post statuses endpoint
  • ISettingsApi - Site settings endpoint
  • IPluginsApi - Plugins management endpoint
  • IThemesApi - Themes management endpoint
  • IJWTAuthApi - JWT authentication endpoints
  • ICustomRequestApi - Generic/custom endpoint support with dynamic routing
  • All interfaces use Refit attributes (GET, POST, DELETE, HEAD) with authorization header support

• Refactored HttpHelper to delegate all HTTP operations to Refit clients

  • Initializes all 15 resource-specific Refit clients in constructors using RestService.For<T>()
  • Added GetAuthHeader() to generate Bearer/Basic auth headers
  • Removed manual HttpRequestMessage construction and SetAuthHeader()
  • Uses CustomRequestApi for generic HTTP operations

Preserved Behavior

• Public API unchanged - all client classes continue working without modification
• Authentication (JWT Bearer, Basic), HttpResponsePreProcessing, and JsonSerializerSettings remain functional
• Error handling and exception types unchanged

Example

Before:

using (HttpRequestMessage requestMessage = new(HttpMethod.Get, route))
{
    SetAuthHeader(isAuthRequired, requestMessage);
    response = await _httpClient.SendAsync(requestMessage).ConfigureAwait(false);
}

After:

string authHeader = isAuthRequired ? GetAuthHeader() : null;
response = await CustomRequestApi.GetAsync(route, authHeader).ConfigureAwait(false);

• Fixes Use Refit for http calls  #379

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Use Refit for http calls </issue_title>
<issue_description>Use reactiveui refit internally for making the http calls.
</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Use Refit for http calls  #379

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[ThomasPe]

create an interface for each resource to be used with Refit @copilot

[Copilot]

create an interface for each resource to be used with Refit @copilot

Created resource-specific Refit interfaces for each WordPress REST API endpoint:

• IPostsApi, IPagesApi, ICommentsApi for content types
• ITagsApi, ICategoriesApi, ITaxonomiesApi for taxonomies
• IUsersApi, IMediaApi for core resources
• IPostTypesApi, IPostStatusesApi for metadata
• ISettingsApi, IPluginsApi, IThemesApi for site management
• IJWTAuthApi for authentication
• ICustomRequestApi for generic/custom endpoints

All interfaces include proper HTTP method attributes (GET, POST, DELETE, HEAD) and authorization header support. (commit 738dd2f)