Updated all references and namespaces to RedisKit

README.md

@@ -1,9 +1,9 @@
-# NRedisKit
+# RedisKit
 > A .NET Standard 2.1 helper library for common Redis client functionality. This project is very much still a work in progress.
 
-This package aims to build upon [NRedisStack](https://github.com/redis/NRedisStack) and provide all the functionality needed to get up and running with a new project utilizing Redis as fast as possible. With **NRedisKit** you can add multiple named Redis connections within the Dependency Injection container _(beneficial in hybrid environments where Redis server setups could be different e.g. persistent vs non-persistent)_, then configure each of these connections with features such as .NET Data Protection keys persistence, an `ITicketStore` implementation to store large Claims Principals from your application's authentication cookies _(very useful within Blazor Server applications where no HTTP Context is available)_, individual health checks to each Redis server, message consumer and producer implementations to make working with Redis Streams more simple as well as many other helpful methods and extensions for working with the [RedisJSON](https://redis.io/docs/data-types/json) and [RediSearch](https://github.com/RediSearch/RediSearch) modules.
+This package aims to build upon [NRedisStack](https://github.com/redis/NRedisStack) and provide all the functionality needed to get up and running with a new project utilizing Redis as fast as possible. With **RedisKit** you can add multiple named Redis connections within the Dependency Injection container _(beneficial in hybrid environments where Redis server setups could be different e.g. persistent vs non-persistent)_, then configure each of these connections with features such as .NET Data Protection keys persistence, an `ITicketStore` implementation to store large Claims Principals from your application's authentication cookies _(very useful within Blazor Server applications where no HTTP Context is available)_, individual health checks to each Redis server, message consumer and producer implementations to make working with Redis Streams more simple as well as many other helpful methods and extensions for working with the [RedisJSON](https://redis.io/docs/data-types/json) and [RediSearch](https://github.com/RediSearch/RediSearch) modules.
 
-[![Build & Test](https://github.com/melittleman/NRedisKit/actions/workflows/build-test.yml/badge.svg)](https://github.com/melittleman/NRedisKit/actions/workflows/build-test.yml)
+[![Build & Test](https://github.com/melittleman/RedisKit/actions/workflows/build-test.yml/badge.svg)](https://github.com/melittleman/RedisKit/actions/workflows/build-test.yml)
 
 ## Contents
 - [Getting Started](#getting-started)
@@ -23,18 +23,18 @@ This package aims to build upon [NRedisStack](https://github.com/redis/NRedisSta
 To get started with this library, you will first need to download and install either the [.NET 8 SDK](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) or Microsoft [Visual Studio 2022](https://visualstudio.microsoft.com/downloads/) which comes bundled with the SDK.
 
 ## Repository Structure
-- **.github** - Files needed by GitHub are contained in the `.github` directory. For example; the `workflows` directory contains any _Build_, _Test_ or _Package_ configurations needed by **GitHub** [**Actions**](https://github.com/melittleman/NRedisKit/actions).
+- **.github** - Files needed by GitHub are contained in the `.github` directory. For example; the `workflows` directory contains any _Build_, _Test_ or _Package_ configurations needed by **GitHub** [**Actions**](https://github.com/melittleman/RedisKit/actions).
 - **src** - The _Source_ directory contains all the source code for the library.
-- **test** - Contains all unit and integration tests relating to the **src** directory. These tests are implemented in [XUnit](https://xunit.net/) and can be run using the ```dotnet test``` CLI. These tests will also be run as part of the [Build & Test](https://github.com/melittleman/NRedisKit/actions/workflows/build-test.yml) workflow in GitHub Actions.
+- **test** - Contains all unit and integration tests relating to the **src** directory. These tests are implemented in [XUnit](https://xunit.net/) and can be run using the ```dotnet test``` CLI. These tests will also be run as part of the [Build & Test](https://github.com/melittleman/RedisKit/actions/workflows/build-test.yml) workflow in GitHub Actions.
 
 ## Usage
-Once you have installed the desired version of **NRedisKit** you can configure this during service registration to be used by an application in the following ways.
+Once you have installed the desired version of **RedisKit** you can configure this during service registration to be used by an application in the following ways.
 
 ### Adding A Named Connection
 You can add a named Redis connection to the Dependency Injection container and configure it by passing in an `Action` of `RedisConnectionOptions`.
 
 ```csharp
-using NRedisKit.DependencyInjection.Extensions;
+using RedisKit.DependencyInjection.Extensions;
 
 services.AddRedisConnection("cloud-cache", options =>
 {
@@ -52,8 +52,8 @@ For example: `redis0:6379,redis1:6380,allowAdmin=true,ssl=false`
 
 This can then be used later anywhere in the application via the Transient `IRedisClientFactory` that retrieves named Redis connections and creates the wrapping client.
 ```csharp
-using NRedisKit;
-using NRedisKit.DependencyInjection.Abstractions;
+using RedisKit;
+using RedisKit.DependencyInjection.Abstractions;
 
 private readonly RedisClient _redis;
 
@@ -70,7 +70,7 @@ public async Task DoSomethingAsync()
 
 If only a single Redis connection is being used within the application, this can then easily be retrieved directly from DI, rather than going via the factory.
 ```csharp
-using NRedisKit;
+using RedisKit;
 
 private readonly RedisClient _redis;
 
@@ -87,8 +87,8 @@ public Task<T> GetSomethingAsync()
 
 You can continue to use a connection in exactly the same ways that you would otherwise use [NRedisStack](https://github.com/redis/NRedisStack) or [StackExchange.Redis](https://github.com/StackExchange/StackExchange.Redis) directly.
 ```csharp
-using NRedisKit;
-using NRedisKit.DependencyInjection.Abstractions;
+using RedisKit;
+using RedisKit.DependencyInjection.Abstractions;
 
 using NRedisStack;
 using NRedisStack.RedisStackCommands;
@@ -121,7 +121,7 @@ The main benefit of configuring these named connections is to be able to connect
 For example; a caching instance that does not have persistence or high availability enabled, and therefore reduces costs. And a Messaging instance, where both persistence and AOF writing may be needed.
 
 ```csharp
-using NRedisKit.DependencyInjection.Extensions;
+using RedisKit.DependencyInjection.Extensions;
 
 services.AddRedisConnection("enterprise-cache", options =>
 {
@@ -143,7 +143,7 @@ The return type of `IServiceCollection.AddRedisConnection()` is a new instance o
 For example, to add the .NET Data Protection middleware to the application that utilizes your named Redis connection:
 
 ```csharp
-using NRedisKit.DependencyInjection.Extensions;
+using RedisKit.DependencyInjection.Extensions;
 
 services
     .AddRedisConnection("elasticache", options...)
@@ -154,7 +154,7 @@ services
 The `RedisClient` is also able to help abstract Redis JSON document usage within the application. You can use your own custom JSON converters for (de)serialization by configuring it in the following way.
 
 ```csharp
-using NRedisKit.DependencyInjection.Extensions;
+using RedisKit.DependencyInjection.Extensions;
 
 services.ConfigureRedisJson(options =>
 {
@@ -164,7 +164,7 @@ services.ConfigureRedisJson(options =>
 
 Use the `RedisClient` in the same way as you would with any of the other built in Redis data types and it will use the configured JSON converters.
 ```csharp
-using NRedisKit;
+using RedisKit;
 
 private readonly RedisClient _redis;
 
@@ -187,7 +187,7 @@ In order to get started simply chain either one or both of the methods below dur
 > **Note**: These do not need to be chained to the same connection. For example you could _Consume_ messages from an internal Redis server and then _Produce_ these out to an entirely different public server.
 
 ```csharp
-using NRedisKit.DependencyInjection.Extensions;
+using RedisKit.DependencyInjection.Extensions;
 
 services
     .AddRedisConnection("message-broker", options...)
@@ -201,7 +201,7 @@ services
 You can then request these abstractions from the Dependency Injection container and use them to produce or consume messages.
 
 ```csharp
-using NRedisKit.Messaging.Abstractions;
+using RedisKit.Messaging.Abstractions;
 
 private readonly IMessageConsumer<MyMessage> _consumer;
 private readonly IMessageProducer<MyMessage> _producer;
@@ -234,7 +234,7 @@ public Task ProduceSomethingAsync(MyMessage message)
 The .NET Data Protection providers can be configured to use your named Redis connection and save the keys under a specified location like the following:
 
 ```csharp
-using NRedisKit.DependencyInjection.Extensions;
+using RedisKit.DependencyInjection.Extensions;
 
 services
     .AddRedisConnection("redis-persistent", options...)
@@ -252,8 +252,8 @@ authentication sessions, and removes the reliance on browsers storing very large
 > **Note**: You MUST ensure that both [JSON document](#json-documents) storage and [Data Protection](#data-protection) has been configured for this to work correctly.
 
 ```csharp
-using NRedisKit.DependencyInjection.Extensions;
-using NRedisKit.Json.Converters;
+using RedisKit.DependencyInjection.Extensions;
+using RedisKit.Json.Converters;
 
 services
     .AddRedisConnection("redis-persistent", options...)
@@ -269,7 +269,7 @@ services
 You can configure the built in .NET Health Check framework to test connectivity to your named Redis connection as part of it's configured Health Checks.
 
 ```csharp
-using NRedisKit.DependencyInjection.Extensions;
+using RedisKit.DependencyInjection.Extensions;
 
 services
     .AddRedisConnection("redis-server", options...)

NRedisKit.sln → RedisKit.sln

@@ -6,9 +6,9 @@ Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "src", "src", "{9686F443-E07
 EndProject
 Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "test", "test", "{5C12C701-9BB2-48FC-A835-5176A592D149}"
 EndProject
-Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "NRedisKit", "src\NRedisKit.csproj", "{34AEEB8C-DF91-4566-8D12-744A4F30FA20}"
+Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "RedisKit", "src\RedisKit.csproj", "{34AEEB8C-DF91-4566-8D12-744A4F30FA20}"
 EndProject
-Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "NRedisKit.UnitTest", "test\UnitTest\NRedisKit.UnitTest.csproj", "{C9B983E8-E79C-4A57-963D-6194DFE4371F}"
+Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "RedisKit.UnitTest", "test\UnitTest\RedisKit.UnitTest.csproj", "{C9B983E8-E79C-4A57-963D-6194DFE4371F}"
 EndProject
 Global
 	GlobalSection(SolutionConfigurationPlatforms) = preSolution

src/Abstractions/IHashEntry.cs

@@ -1,4 +1,4 @@
-namespace NRedisKit.Abstractions;
+namespace RedisKit.Abstractions;
 
 public interface IHashEntry
 {

src/Abstractions/IRedisContext.cs

@@ -1,4 +1,4 @@
-namespace NRedisKit.Abstractions;
+namespace RedisKit.Abstractions;
 
 /// <summary>
 ///     <para>The Redis connection context.</para>

src/Abstractions/ISortedSetEntry.cs

@@ -1,4 +1,4 @@
-namespace NRedisKit.Abstractions;
+namespace RedisKit.Abstractions;
 
 public interface ISortedSetEntry
 {

src/Abstractions/ITaggedEntry.cs

@@ -1,4 +1,4 @@
-namespace NRedisKit.Abstractions;
+namespace RedisKit.Abstractions;
 
 public interface ITaggedEntry
 {

src/Authentication/RedisTicketStore.cs

@@ -8,7 +8,7 @@
 using NRedisStack;
 using NRedisStack.RedisStackCommands;
 
-namespace NRedisKit.Authentication;
+namespace RedisKit.Authentication;
 
 /// <summary>
 ///     A custom <see cref="AuthenticationTicket"/> storage implementation of <see cref="ITicketStore"/> using

src/DependencyInjection/Abstractions/IRedisClientFactory.cs

@@ -1,4 +1,4 @@
-namespace NRedisKit.DependencyInjection.Abstractions;
+namespace RedisKit.DependencyInjection.Abstractions;
 
 public interface IRedisClientFactory
 {

src/DependencyInjection/Abstractions/IRedisConnectionBuilder.cs

@@ -1,6 +1,6 @@
 using Microsoft.Extensions.DependencyInjection;
 
-namespace NRedisKit.DependencyInjection.Abstractions;
+namespace RedisKit.DependencyInjection.Abstractions;
 
 /// <summary>
 ///     A fluent helper when building Redis connections that

src/DependencyInjection/Abstractions/IRedisConnectionProvider.cs

@@ -1,6 +1,6 @@
 using System.Collections.Concurrent;
 
-namespace NRedisKit.DependencyInjection.Abstractions;
+namespace RedisKit.DependencyInjection.Abstractions;
 
 /// <summary>
 ///     A singleton container around multiple pooled Redis connections.

src/DependencyInjection/DefaultRedisClientFactory.cs

@@ -1,6 +1,6 @@
 using Microsoft.Extensions.Options;
 
-namespace NRedisKit.DependencyInjection;
+namespace RedisKit.DependencyInjection;
 
 internal sealed record DefaultRedisClientFactory : IRedisClientFactory
 {

src/DependencyInjection/DefaultRedisConnectionBuilder.cs

@@ -1,6 +1,6 @@
 using Microsoft.Extensions.DependencyInjection;
 
-namespace NRedisKit.DependencyInjection;
+namespace RedisKit.DependencyInjection;
 
 /// <inheritdoc />
 internal sealed record DefaultRedisConnectionBuilder : IRedisConnectionBuilder

src/DependencyInjection/DefaultRedisConnectionProvider.cs

@@ -3,7 +3,7 @@
 using Microsoft.Extensions.Hosting;
 using Microsoft.Extensions.Options;
 
-namespace NRedisKit.DependencyInjection;
+namespace RedisKit.DependencyInjection;
 
 /// <inheritdoc />
 internal sealed record DefaultRedisConnectionProvider : IRedisConnectionProvider

src/DependencyInjection/Extensions/RedisConnectionBuilderExtensions.cs

@@ -12,14 +12,14 @@
 using OpenTelemetry.Trace;
 using OpenTelemetry.Instrumentation.StackExchangeRedis;
 
-using NRedisKit.Diagnostics;
-using NRedisKit.Authentication;
-using NRedisKit.Messaging;
-using NRedisKit.Messaging.Constants;
-using NRedisKit.Messaging.Abstractions;
-using NRedisKit.Json.Converters;
-
-namespace NRedisKit.DependencyInjection.Extensions;
+using RedisKit.Diagnostics;
+using RedisKit.Authentication;
+using RedisKit.Messaging;
+using RedisKit.Messaging.Constants;
+using RedisKit.Messaging.Abstractions;
+using RedisKit.Json.Converters;
+
+namespace RedisKit.DependencyInjection.Extensions;
 
 public static class RedisConnectionBuilderExtensions
 {

src/DependencyInjection/Extensions/ServiceCollectionExtensions.cs

@@ -3,7 +3,7 @@
 using Microsoft.Extensions.DependencyInjection;
 using Microsoft.Extensions.DependencyInjection.Extensions;
 
-namespace NRedisKit.DependencyInjection.Extensions;
+namespace RedisKit.DependencyInjection.Extensions;
 
 public static class ServiceCollectionExtensions
 {

src/DependencyInjection/Options/RedisAuthenticationTicketOptions.cs

@@ -1,4 +1,4 @@
-namespace NRedisKit.DependencyInjection.Options;
+namespace RedisKit.DependencyInjection.Options;
 
 public sealed record RedisAuthenticationTicketOptions
 {

src/DependencyInjection/Options/RedisConnectionOptions.cs

@@ -1,4 +1,4 @@
-namespace NRedisKit.DependencyInjection.Options;
+namespace RedisKit.DependencyInjection.Options;
 
 public sealed record RedisConnectionOptions
 {

src/DependencyInjection/Options/RedisDataProtectionOptions.cs

@@ -1,4 +1,4 @@
-namespace NRedisKit.DependencyInjection.Options;
+namespace RedisKit.DependencyInjection.Options;
 
 public sealed record RedisDataProtectionOptions
 {

src/DependencyInjection/Options/RedisJsonOptions.cs

@@ -1,6 +1,6 @@
 using System.Text.Json;
 
-namespace NRedisKit.DependencyInjection.Options;
+namespace RedisKit.DependencyInjection.Options;
 
 public sealed record RedisJsonOptions
 {

src/DependencyInjection/Options/RedisMessagingOptions.cs

@@ -1,4 +1,4 @@
-namespace NRedisKit.DependencyInjection.Options;
+namespace RedisKit.DependencyInjection.Options;
 
 // TODO: We may eventually need to look at creating specific options
 // betwee Producers and Consumers as currently they both use the same IOptions

src/Diagnostics/RedisHealthCheck.cs

@@ -3,7 +3,7 @@
 
 using Microsoft.Extensions.Diagnostics.HealthChecks;
 
-namespace NRedisKit.Diagnostics;
+namespace RedisKit.Diagnostics;
 
 /// <inheritdoc />
 internal sealed record RedisHealthCheck : IHealthCheck

src/Extensions/ConfigurationOptionsExtensions.cs

@@ -1,6 +1,6 @@
 using System.Text.RegularExpressions;
 
-namespace NRedisKit.Extensions;
+namespace RedisKit.Extensions;
 
 internal static class ConfigurationOptionsExtensions
 {

src/Extensions/DocumentExtensions.cs

@@ -3,7 +3,7 @@
 
 using NRedisStack.Search;
 
-namespace NRedisKit.Extensions;
+namespace RedisKit.Extensions;
 
 public static class DocumentExtensions
 {

src/Extensions/GuidExtensions.cs

@@ -1,4 +1,4 @@
-namespace NRedisKit.Extensions;
+namespace RedisKit.Extensions;
 
 public static class GuidExtensions
 {

src/Extensions/HashEntryExtensions.cs

@@ -1,7 +1,7 @@
 using System.Linq;
 using System.Reflection;
 
-namespace NRedisKit.Extensions;
+namespace RedisKit.Extensions;
 
 public static class HashEntryExtensions
 {

src/Extensions/NameValueExtensions.cs

@@ -1,7 +1,7 @@
 using System.Linq;
 using System.Reflection;
 
-namespace NRedisKit.Extensions;
+namespace RedisKit.Extensions;
 
 public static class NameValueExtensions
 {

src/Extensions/RedisValueExtensions.cs

@@ -2,7 +2,7 @@
 using System.Globalization;
 using System.Text.Json;
 
-namespace NRedisKit.Extensions;
+namespace RedisKit.Extensions;
 
 internal static class RedisValueExtensions
 {

src/Extensions/SortedSetEntryExtensions.cs

@@ -1,7 +1,7 @@
 using System.Collections.Generic;
 using System.Linq;
 
-namespace NRedisKit.Extensions;
+namespace RedisKit.Extensions;
 
 public static class SortedSetEntryExtensions
 {   

src/Extensions/StreamEntryExtensions.cs

@@ -1,6 +1,6 @@
 using System.Linq;
 
-namespace NRedisKit.Extensions;
+namespace RedisKit.Extensions;
 
 public static class StreamEntryExtensions
 {

src/Extensions/StringExtensions.cs

@@ -1,6 +1,6 @@
 using System.ComponentModel;
 
-namespace NRedisKit.Extensions;
+namespace RedisKit.Extensions;
 
 public static class StringExtensions
 {