Rystem.RepositoryFramework.Abstractions
0.8.1
See the version list below for details.
dotnet add package Rystem.RepositoryFramework.Abstractions --version 0.8.1
NuGet\Install-Package Rystem.RepositoryFramework.Abstractions -Version 0.8.1
<PackageReference Include="Rystem.RepositoryFramework.Abstractions" Version="0.8.1" />
paket add Rystem.RepositoryFramework.Abstractions --version 0.8.1
#r "nuget: Rystem.RepositoryFramework.Abstractions, 0.8.1"
// Install Rystem.RepositoryFramework.Abstractions as a Cake Addin #addin nuget:?package=Rystem.RepositoryFramework.Abstractions&version=0.8.1 // Install Rystem.RepositoryFramework.Abstractions as a Cake Tool #tool nuget:?package=Rystem.RepositoryFramework.Abstractions&version=0.8.1
Repository Framework
Contribute: https://www.buymeacoffee.com/keyserdsoze
Showcase (youtube)
Showcase (code)
Rystem.RepositoryFramework allows you to use correctly concepts like repository pattern, CQRS and DDD. You have interfaces for your domains, auto-generated api, auto-generated HttpClient to simplify connection "api to front-end", a functionality for auto-population in memory of your models, a functionality to simulate exceptions and waiting time from external sources to improve your implementation/business test and load test.
Document to read before using this library:
- Repository pattern, useful links:
- CQRS, useful links:
- DDD, useful links:
Basic knowledge
Interfaces
Based on CQRS we could split our repository pattern in two main interfaces, one for update (write, delete) and one for read.
Command (Write-Delete)
public interface ICommand<T, TKey> : ICommandPattern
where TKey : notnull
{
Task<bool> InsertAsync(TKey key, T value, CancellationToken cancellationToken = default);
Task<bool> UpdateAsync(TKey key, T value, CancellationToken cancellationToken = default);
Task<bool> DeleteAsync(TKey key, CancellationToken cancellationToken = default);
}
Query (Read)
public interface IQuery<T, TKey> : IQueryPattern
where TKey : notnull
{
Task<T?> GetAsync(TKey key, CancellationToken cancellationToken = default);
Task<IEnumerable<T>> QueryAsync(Expression<Func<T, bool>>? predicate = null, int? top = null, int? skip = null, CancellationToken cancellationToken = default);
}
Repository Pattern (Write-Delete-Read)
public interface IRepository<T, TKey> : ICommand<T, TKey>, IQuery<T, TKey>, IRepositoryPattern, ICommandPattern, IQueryPattern
where TKey : notnull
{
}
Examples
Model
public class User
{
public string Id { get; set; }
public string Name { get; set; }
public string Email { get; set; }
}
Command
public class UserWriter : ICommand<User, string>
{
public Task<bool> DeleteAsync(string key, CancellationToken cancellationToken = default)
{
//delete on with DB or storage context
throw new NotImplementedException();
}
public Task<bool> InsertAsync(string key, User value, CancellationToken cancellationToken = default)
{
//insert on DB or storage context
throw new NotImplementedException();
}
public Task<bool> UpdateAsync(string key, User value, CancellationToken cancellationToken = default)
{
//update on DB or storage context
throw new NotImplementedException();
}
}
Query
public class UserReader : IQuery<User, string>
{
public Task<User?> GetAsync(string key, CancellationToken cancellationToken = default)
{
//get an item by key from DB or storage context
throw new NotImplementedException();
}
public Task<IEnumerable<User>> QueryAsync(Expression<Func<User, bool>>? predicate = null, int? top = null, int? skip = null, CancellationToken cancellationToken = default)
{
//get a list of items by a predicate with top and skip from DB or storage context
throw new NotImplementedException();
}
}
Alltogether as repository pattern
if you don't have CQRS infrastructure (usually it's correct to use CQRS when you have minimum two infrastructures one for write and delete and at least one for read)
public class UserRepository : IRepository<User, string>, IQuery<User, string>, ICommand<User, string>
{
public Task<bool> DeleteAsync(string key, CancellationToken cancellationToken = default)
{
//delete on with DB or storage context
throw new NotImplementedException();
}
public Task<bool> InsertAsync(string key, User value, CancellationToken cancellationToken = default)
{
//insert on DB or storage context
throw new NotImplementedException();
}
public Task<bool> UpdateAsync(string key, User value, CancellationToken cancellationToken = default)
{
//update on DB or storage context
throw new NotImplementedException();
}
public Task<User?> GetAsync(string key, CancellationToken cancellationToken = default)
{
//get an item by key from DB or storage context
throw new NotImplementedException();
}
public Task<IEnumerable<User>> QueryAsync(Expression<Func<User, bool>>? predicate = null, int? top = null, int? skip = null, CancellationToken cancellationToken = default)
{
//get a list of items by a predicate with top and skip from DB or storage context
throw new NotImplementedException();
}
}
Specific key interfaces
You may use specific interfaces for 4 specific classic keys: Int, Long, Guid, String
Command for Guid (Write-Delete)
public interface IGuidableCommand<T> : ICommand<T, Guid>, ICommandPattern
{
}
Query for Guid (Read)
public interface IGuidableQuery<T> : IQuery<T, Guid>, IQueryPattern
{
}
Repository Pattern for Guid (Write-Delete-Read)
public interface IGuidableRepository<T> : IRepository<T, Guid>, IGuidableCommand<T>, IGuidableQuery<T>, IRepositoryPattern, IQueryPattern, ICommandPattern { }
String key
interface IStringableCommand<T> : ICommand<T,string>, ICommandPattern
interface IStringableQuery<T> : IQuery<T, string>, IQueryPattern
interface IStringableRepository<T> : IRepository<T, string>, IStringableCommand<T>, IStringableQuery<T>, IRepositoryPattern, ICommandPattern, IQueryPattern
Int key
interface IIntableCommand<T> : ICommand<T, int>, ICommandPattern
interface IIntableQuery<T> : IQuery<T, int>, IQueryPattern
interface IIntableRepository<T> : IRepository<T, int>, IIntableCommand<T>, IIntableQuery<T>, IRepositoryPattern, IQueryPattern, ICommandPattern
Long key
interface ILongableCommand<T> : ICommand<T, long>, ICommandPattern
interface ILongableQuery<T> : IQuery<T, long>, IQueryPattern
interface ILongableRepository<T> : IRepository<T, long>, ILongableCommand<T>, ILongableQuery<T>, IRepositoryPattern
Dependency Injection
IServiceCollection extension methods
You can use these extension methods to have a simple mechanic to integrate with .Net DI pattern, by default it's integrated with scoped service life time but you can choose another one at your discretion. You may find them in Microsoft.Extensions.DependencyInjection namespace.
Add Command pattern
public static IServiceCollection AddCommand<T, TKey, TStorage>(this IServiceCollection services,
ServiceLifetime serviceLifetime = ServiceLifetime.Scoped)
where TStorage : class, ICommand<T, TKey>
where TKey : notnull
Add Query pattern
public static IServiceCollection AddQuery<T, TKey, TStorage>(this IServiceCollection services,
ServiceLifetime serviceLifetime = ServiceLifetime.Scoped)
where TStorage : class, IQuery<T, TKey>
where TKey : notnull
Add Repository pattern
As before you may choose to use repository pattern instead CQRS.
public static IServiceCollection AddRepository<T, TKey, TStorage>(this IServiceCollection services,
ServiceLifetime serviceLifetime = ServiceLifetime.Scoped)
where TStorage : class, IRepository<T, TKey>
where TKey : notnull
Add Command&Query or Repository with specific keys
An example with Guid, valid also for String, Int, Long
public static IServiceCollection AddRepositoryWithGuidKey<T, TStorage>(this IServiceCollection services,
ServiceLifetime serviceLifetime = ServiceLifetime.Scoped)
where TStorage : class, IGuidableRepository<T>
public static IServiceCollection AddCommandWithGuidKey<T, TStorage>(this IServiceCollection services,
ServiceLifetime serviceLifetime = ServiceLifetime.Scoped)
where TStorage : class, IGuidableCommand<T>
public static IServiceCollection AddQueryWithGuidKey<T, TStorage>(this IServiceCollection services,
ServiceLifetime serviceLifetime = ServiceLifetime.Scoped)
where TStorage : class, IGuidableQuery<T>
How to use it in DI?
You have only to inject the interface you added everywhere you need it. Below an example from unit test.
public class RandomCreationTest
{
private readonly IStringableRepository<PopulationTest> _test;
private readonly IRepository<RegexPopulationTest, double> _population;
private readonly IStringableQuery<DelegationPopulation> _delegation;
public RandomCreationTest(IStringableRepository<PopulationTest> test,
IRepository<RegexPopulationTest, double> population,
IStringableQuery<DelegationPopulation> delegation)
{
_test = test;
_population = population;
_delegation = delegation;
}
}
Api auto-generated
In your web application you have only to add one row.
app.AddApiForRepositoryFramework();
Startup example
In the example below you may find the DI for repository with string key for User model, populated with random data in memory, swagger to test the solution, the population method just after the build and the configuration of your API based on repository framework.
using RepositoryFramework.WebApi.Models;
var builder = WebApplication.CreateBuilder(args);
builder.Services
.AddRepositoryInMemoryStorageWithStringKey<User>()
.PopulateWithRandomData(x => x.Email!, 120, 5);
builder.Services.AddEndpointsApiExplorer();
builder.Services.AddSwaggerGen();
var app = builder.Build();
app.Services.Populate();
// Configure the HTTP request pipeline.
if (app.Environment.IsDevelopment())
{
app.UseSwagger();
app.UseSwaggerUI();
}
app.UseHttpsRedirection();
app.AddApiForRepositoryFramework();
app.Run();
HttpClient to use your API (example)
You can add a client for a specific url
.AddRepositoryClient<User, string>("localhost:7058");
and use it in DI with
IRepositoryClient<User, string>
Integration for specific key
Here an example for Guid, you may find the same Client for Int, Long, String
.AddRepositoryClientWithGuidKey<User>("localhost:7058");
that injects
IGuidableRepositoryClient<User>
Integration for Command or Query
.AddCommandClient<User, string>("localhost:7058");
or
.AddQueryClient<User, string>("localhost:7058");
In memory integration by default
With this library you can add in memory integration with the chance to create random data with random values, random based on regular expressions and delegated methods
public static RepositoryInMemoryBuilder<T, TKey> AddRepositoryInMemoryStorage<T, TKey>(
this IServiceCollection services,
Action<RepositoryBehaviorSettings<T, TKey>>? settings = default)
where TKey : notnull
Populate with specific key (example with Guid)
public RepositoryInMemoryBuilder<TNext, Guid> AddRepositoryInMemoryStorageWithGuidKey<TNext>(Action<RepositoryBehaviorSettings<TNext, Guid>>? settings = default)
How to populate with random data?
Simple random (example)
Populate your in memory storage with 120 users
var builder = WebApplication.CreateBuilder(args);
builder.Services.AddRepositoryInMemoryStorageWithStringKey<User>()
.PopulateWithRandomData(x => x.Email!, 120);
and in app after build during startup of your application
var app = builder.Build();
app.Services.Populate();
Simple random with regex (example)
Populate your in memory storage with 100 users and property Email with a random regex @"[a-z]{4,10}@gmail.com"
.AddRepositoryInMemoryStorage<User, string>()
.PopulateWithRandomData()
.WithPattern(x => x.Email, @"[a-z]{4,10}@gmail\.com")
.Populate(x => x.Id!, 100)
Where can I use the regex pattern?
You can use regex pattern on all primitives type and most used structs.
Complete list:
int, uint, byte, sbyte, short, ushort, long, ulong, nint, nuint, float, double, decimal, bool, char, Guid, DateTime, TimeSpan, Range, string, int?, uint?, byte?, sbyte?, short?, ushort?, long?, ulong?, nint?, nuint?, float?, double?, decimal?, bool?, char?, Guid?, DateTime?, TimeSpan?, Range?, string?
You can use the pattern in Class, IEnumerable, IDictionary, or Array, and in everything that extends IEnumerable or IDictionary
Important!! You can override regex service in your DI
public static IServiceCollection AddRegexService<T>(
this IServiceCollection services)
where T : class, IRegexService
IEnumerable or Array one-dimension (example)
You have your model x (User) that has a property Groups as IEnumerable or something that extends IEnumerable, Groups is a class with a property Id as string. In the code below you are creating a list of class Groups with 8 elements in each 100 User instances, in each element of Groups you randomize based on this regex "[a-z]{4,5}". You may take care of use First() linq method to set correctly the Id property.
.AddRepositoryInMemoryStorage<User, string>()
.PopulateWithRandomData(x => x.Id!, 100, 8)
.WithPattern(x => x.Groups!.First().Id, "[a-z]{4,5}")
and after build in your startup
app.Services.Populate()
IDictionary (example)
Similar to IEnumerable population you may populate your Claims property (a dictionary) with random key but with values based on regular expression "[a-z]{4,5}". As well as IEnumerable implementation you will have 6 elements (because I choose to create 6 elements in Populate method)
.AddRepositoryInMemoryStorage<User, string>()
.PopulateWithRandomData(x => x.Id!, 100, 6)
.WithPattern(x => x.Claims!.First().Value, "[a-z]{4,5}")
and after build in your startup
app.Services.Populate()
or if you have in Value an object
AddRepositoryInMemoryStorage<User, string>()
.PopulateWithRandomData(x => x.Id!, 100, 6)
.WithPattern(x => x.Claims!.First().Value.SomeProperty, "[a-z]{4,5}")
and after build in your startup
app.Services.Populate()
Populate with delegation
Similar to regex pattern, you can use a delegation to populate something.
Dictionary (example)
Here you can see that all 6 elements in each 100 users are populated in Value with string "A"
.AddRepositoryPatternInMemoryStorage<User, string>()
.PopulateWithRandomData(x => x.Id!, 100, 6)
.WithPattern(x => x.Claims!.First().Value, () => "A"))
and after build in your startup
app.Services.Populate()
Populate with Implementation
If you have an interface or abstraction in your model, you can specify an implementation type for population. You have two different methods, with typeof
.AddRepositoryInMemoryStorageWithStringKey<PopulationTest>()
.PopulateWithRandomData()
.WithImplementation(x => x.I, typeof(MyInnerInterfaceImplementation))
or generics
.AddRepositoryInMemoryStorageWithStringKey<PopulationTest>()
.PopulateWithRandomData()
.WithImplementation<IInnerInterface, MyInnerInterfaceImplementation>(x => x.I!)
In Memory, simulate real implementation
If you want to test with possible exceptions (for your reliability tests) and waiting time (for your load tests) you may do it with this library and in memory behavior settings.
Add random exceptions
You can set different custom exceptions and different percentage for each operation: Delete, Get, Insert, Update, Query. In the code below I'm adding three exceptions with a percentage of throwing them, they are the same for each operation. I have a 0.45% for normal Exception, 0.1% for "Big Exception" and 0.548% for "Great Exception"
.AddRepositoryInMemoryStorage<User, string>(options =>
{
var customExceptions = new List<ExceptionOdds>
{
new ExceptionOdds()
{
Exception = new Exception(),
Percentage = 0.45
},
new ExceptionOdds()
{
Exception = new Exception("Big Exception"),
Percentage = 0.1
},
new ExceptionOdds()
{
Exception = new Exception("Great Exception"),
Percentage = 0.548
}
};
options.ExceptionOddsForDelete.AddRange(customExceptions);
options.ExceptionOddsForGet.AddRange(customExceptions);
options.ExceptionOddsForInsert.AddRange(customExceptions);
options.ExceptionOddsForUpdate.AddRange(customExceptions);
options.ExceptionOddsForQuery.AddRange(customExceptions);
})
Add random waiting time
You can set different range in milliseconds for each operation. In the code below I'm adding a same custom range for Delete, Insert, Update, Get between 1000ms and 2000ms, and a unique custom range for Query between 3000ms and 7000ms.
.AddRepositoryInMemoryStorage<User, string>(options =>
{
var customRange = new Range(1000, 2000);
options.MillisecondsOfWaitForDelete = customRange;
options.MillisecondsOfWaitForInsert = customRange;
options.MillisecondsOfWaitForUpdate = customRange;
options.MillisecondsOfWaitForGet = customRange;
options.MillisecondsOfWaitForQuery = new Range(3000, 7000);
})
Add random waiting time before an exception
You can set different range in milliseconds for each operation before to throw an exception. In the code below I'm adding a same custom range for Delete, Insert, Update, Get between 1000ms and 2000ms, and a unique custom range for Query between 3000ms and 7000ms in case of exception.
.AddRepositoryInMemoryStorage<User, string>(options =>
{
var customRange = new Range(1000, 2000);
options.MillisecondsOfWaitBeforeExceptionForDelete = customRange;
options.MillisecondsOfWaitBeforeExceptionForInsert = customRange;
options.MillisecondsOfWaitBeforeExceptionForUpdate = customRange;
options.MillisecondsOfWaitBeforeExceptionForGet = customRange;
options.MillisecondsOfWaitBeforeExceptionForQuery = new Range(3000, 7000);
var customExceptions = new List<ExceptionOdds>
{
new ExceptionOdds()
{
Exception = new Exception(),
Percentage = 0.45
},
new ExceptionOdds()
{
Exception = new Exception("Big Exception"),
Percentage = 0.1
},
new ExceptionOdds()
{
Exception = new Exception("Great Exception"),
Percentage = 0.548
}
};
options.ExceptionOddsForDelete.AddRange(customExceptions);
options.ExceptionOddsForGet.AddRange(customExceptions);
options.ExceptionOddsForInsert.AddRange(customExceptions);
options.ExceptionOddsForUpdate.AddRange(customExceptions);
options.ExceptionOddsForQuery.AddRange(customExceptions);
})
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net6.0 is compatible. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
-
net6.0
- No dependencies.
NuGet packages (12)
Showing the top 5 NuGet packages that depend on Rystem.RepositoryFramework.Abstractions:
Package | Downloads |
---|---|
Rystem.RepositoryFramework.Api.Server
Rystem.RepositoryFramework allows you to use correctly concepts like repository pattern, CQRS and DDD. You have interfaces for your domains, auto-generated api, auto-generated HttpClient to simplify connection "api to front-end", a functionality for auto-population in memory of your models, a functionality to simulate exceptions and waiting time from external sources to improve your implementation/business test and load test. |
|
Rystem.RepositoryFramework.Api.Client
Rystem.RepositoryFramework allows you to use correctly concepts like repository pattern, CQRS and DDD. You have interfaces for your domains, auto-generated api, auto-generated HttpClient to simplify connection "api to front-end", a functionality for auto-population in memory of your models, a functionality to simulate exceptions and waiting time from external sources to improve your implementation/business test and load test. |
|
Rystem.RepositoryFramework.Infrastructure.Azure.Storage.Blob
Rystem.RepositoryFramework allows you to use correctly concepts like repository pattern, CQRS and DDD. You have interfaces for your domains, auto-generated api, auto-generated HttpClient to simplify connection "api to front-end", a functionality for auto-population in memory of your models, a functionality to simulate exceptions and waiting time from external sources to improve your implementation/business test and load test. |
|
Rystem.RepositoryFramework.Infrastructure.Azure.Storage.Table
Rystem.RepositoryFramework allows you to use correctly concepts like repository pattern, CQRS and DDD. You have interfaces for your domains, auto-generated api, auto-generated HttpClient to simplify connection "api to front-end", a functionality for auto-population in memory of your models, a functionality to simulate exceptions and waiting time from external sources to improve your implementation/business test and load test. |
|
Rystem.RepositoryFramework.Cache
Rystem.RepositoryFramework allows you to use correctly concepts like repository pattern, CQRS and DDD. You have interfaces for your domains, auto-generated api, auto-generated HttpClient to simplify connection "api to front-end", a functionality for auto-population in memory of your models, a functionality to simulate exceptions and waiting time from external sources to improve your implementation/business test and load test. |
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
9.0.0-rc.1 | 125 | 10/18/2024 |
6.2.0 | 182,123 | 10/9/2024 |
6.1.1 | 212 | 10/9/2024 |
6.1.0 | 48,080 | 9/29/2024 |
6.0.24 | 348 | 9/11/2024 |
6.0.23 | 340,252 | 7/18/2024 |
6.0.21 | 286 | 6/18/2024 |
6.0.20 | 727,869 | 6/16/2024 |
6.0.19 | 30,678 | 6/14/2024 |
6.0.18 | 255 | 6/14/2024 |
6.0.17 | 258 | 6/14/2024 |
6.0.16 | 50,123 | 6/10/2024 |
6.0.15 | 267 | 6/9/2024 |
6.0.14 | 94,588 | 5/24/2024 |
6.0.13 | 270 | 5/23/2024 |
6.0.12 | 227 | 5/23/2024 |
6.0.11 | 297 | 5/20/2024 |
6.0.9 | 288 | 5/19/2024 |
6.0.7 | 257 | 5/18/2024 |
6.0.6 | 287 | 5/10/2024 |
6.0.5 | 231 | 5/10/2024 |
6.0.4 | 550,227 | 4/3/2024 |
6.0.3 | 1,504 | 3/25/2024 |
6.0.2 | 378,190 | 3/11/2024 |
6.0.1 | 51,170 | 3/8/2024 |
6.0.0 | 1,171,995 | 11/21/2023 |
6.0.0-rc.6 | 140 | 10/25/2023 |
6.0.0-rc.5 | 107 | 10/25/2023 |
6.0.0-rc.4 | 96 | 10/23/2023 |
6.0.0-rc.3 | 82 | 10/19/2023 |
6.0.0-rc.2 | 121 | 10/18/2023 |
6.0.0-rc.1 | 133 | 10/16/2023 |
5.0.20 | 641,466 | 9/25/2023 |
5.0.19 | 3,185 | 9/10/2023 |
5.0.18 | 2,455 | 9/6/2023 |
5.0.17 | 2,353 | 9/6/2023 |
5.0.16 | 2,408 | 9/5/2023 |
5.0.15 | 2,365 | 9/5/2023 |
5.0.14 | 2,379 | 9/5/2023 |
5.0.13 | 2,441 | 9/1/2023 |
5.0.12 | 2,303 | 8/31/2023 |
5.0.11 | 2,326 | 8/30/2023 |
5.0.10 | 2,361 | 8/29/2023 |
5.0.9 | 2,419 | 8/24/2023 |
5.0.8 | 2,467 | 8/24/2023 |
5.0.7 | 451,919 | 8/23/2023 |
5.0.6 | 19,822 | 8/21/2023 |
5.0.5 | 6,572 | 8/21/2023 |
5.0.4 | 2,474 | 8/16/2023 |
5.0.3 | 214,998 | 8/2/2023 |
5.0.2 | 4,289 | 8/2/2023 |
5.0.1 | 14,041 | 8/1/2023 |
5.0.0 | 14,445 | 7/31/2023 |
4.1.26 | 143,321 | 7/20/2023 |
4.1.25 | 27,130 | 7/16/2023 |
4.1.24 | 400,537 | 6/13/2023 |
4.1.23 | 48,212 | 6/13/2023 |
4.1.22 | 132,166 | 5/30/2023 |
4.1.21 | 58,194 | 5/20/2023 |
4.1.20 | 407,569 | 4/19/2023 |
4.1.19 | 98,335 | 3/20/2023 |
4.1.18 | 2,889 | 3/20/2023 |
4.1.17 | 3,141 | 3/16/2023 |
4.1.16 | 2,886 | 3/16/2023 |
4.1.15 | 2,842 | 3/15/2023 |
4.1.14 | 10,561 | 3/9/2023 |
4.1.13 | 2,993 | 3/7/2023 |
4.1.12 | 3,450 | 2/9/2023 |
4.1.11 | 3,052 | 1/26/2023 |
4.1.10 | 3,275 | 1/22/2023 |
4.1.9 | 2,936 | 1/20/2023 |
4.1.8 | 3,211 | 1/18/2023 |
4.1.7 | 3,164 | 1/18/2023 |
4.1.6 | 3,231 | 1/17/2023 |
4.1.1 | 3,188 | 1/4/2023 |
4.1.0 | 3,070 | 1/1/2023 |
3.1.5 | 3,020 | 12/21/2022 |
3.1.4 | 1,537 | 12/21/2022 |
3.1.3 | 3,329 | 12/12/2022 |
3.1.2 | 3,081 | 12/7/2022 |
3.1.1 | 3,169 | 12/7/2022 |
3.1.0 | 3,149 | 12/1/2022 |
3.0.29 | 3,116 | 12/1/2022 |
3.0.28 | 3,947 | 12/1/2022 |
3.0.27 | 3,319 | 11/23/2022 |
3.0.25 | 6,882 | 11/23/2022 |
3.0.24 | 4,539 | 11/18/2022 |
3.0.23 | 4,214 | 11/18/2022 |
3.0.22 | 4,354 | 11/15/2022 |
3.0.21 | 4,393 | 11/14/2022 |
3.0.20 | 4,459 | 11/13/2022 |
3.0.19 | 4,751 | 11/2/2022 |
3.0.18 | 4,489 | 11/2/2022 |
3.0.17 | 4,567 | 10/29/2022 |
3.0.16 | 4,644 | 10/29/2022 |
3.0.15 | 1,635 | 10/29/2022 |
3.0.14 | 7,473 | 10/24/2022 |
3.0.13 | 4,692 | 10/24/2022 |
3.0.12 | 4,702 | 10/17/2022 |
3.0.11 | 4,655 | 10/10/2022 |
3.0.10 | 4,214 | 10/6/2022 |
3.0.9 | 4,142 | 10/6/2022 |
3.0.8 | 4,116 | 10/6/2022 |
3.0.7 | 4,226 | 10/6/2022 |
3.0.6 | 4,220 | 10/5/2022 |
3.0.5 | 4,120 | 10/5/2022 |
3.0.4 | 4,190 | 10/5/2022 |
3.0.3 | 4,170 | 10/3/2022 |
3.0.2 | 4,230 | 9/30/2022 |
3.0.1 | 4,173 | 9/29/2022 |
3.0.0 | 1,671 | 9/29/2022 |
2.0.17 | 3,811 | 9/29/2022 |
2.0.16 | 4,292 | 9/27/2022 |
2.0.15 | 4,402 | 9/27/2022 |
2.0.14 | 4,307 | 9/26/2022 |
2.0.13 | 4,231 | 9/26/2022 |
2.0.12 | 4,227 | 9/26/2022 |
2.0.11 | 4,165 | 9/25/2022 |
2.0.10 | 4,372 | 9/25/2022 |
2.0.9 | 4,241 | 9/22/2022 |
2.0.8 | 4,161 | 9/22/2022 |
2.0.7 | 1,679 | 9/22/2022 |
2.0.6 | 4,173 | 9/20/2022 |
2.0.5 | 4,369 | 9/20/2022 |
2.0.4 | 4,250 | 9/20/2022 |
2.0.2 | 4,267 | 9/20/2022 |
2.0.1 | 4,490 | 9/13/2022 |
2.0.0 | 4,355 | 8/19/2022 |
1.1.24 | 4,375 | 7/30/2022 |
1.1.23 | 4,314 | 7/29/2022 |
1.1.22 | 4,124 | 7/29/2022 |
1.1.21 | 4,528 | 7/29/2022 |
1.1.20 | 4,291 | 7/29/2022 |
1.1.19 | 4,320 | 7/27/2022 |
1.1.17 | 4,334 | 7/27/2022 |
1.1.16 | 4,331 | 7/26/2022 |
1.1.15 | 4,368 | 7/25/2022 |
1.1.14 | 4,330 | 7/25/2022 |
1.1.13 | 4,227 | 7/22/2022 |
1.1.12 | 4,224 | 7/19/2022 |
1.1.11 | 4,301 | 7/19/2022 |
1.1.10 | 4,273 | 7/19/2022 |
1.1.9 | 4,319 | 7/19/2022 |
1.1.8 | 4,372 | 7/18/2022 |
1.1.7 | 4,208 | 7/18/2022 |
1.1.6 | 4,298 | 7/18/2022 |
1.1.5 | 4,292 | 7/17/2022 |
1.1.4 | 1,653 | 7/17/2022 |
1.1.3 | 6,811 | 7/17/2022 |
1.1.2 | 4,350 | 7/17/2022 |
1.1.1 | 1,686 | 7/17/2022 |
1.1.0 | 4,290 | 7/17/2022 |
1.0.2 | 4,295 | 7/15/2022 |
1.0.1 | 2,980 | 7/15/2022 |
1.0.0 | 5,486 | 7/8/2022 |
0.10.7 | 4,300 | 7/7/2022 |
0.10.6 | 1,746 | 7/7/2022 |
0.10.3 | 2,197 | 7/7/2022 |
0.10.2 | 5,743 | 7/2/2022 |
0.10.1 | 4,301 | 7/1/2022 |
0.10.0 | 4,101 | 7/1/2022 |
0.9.10 | 5,404 | 6/20/2022 |
0.9.9 | 4,343 | 6/11/2022 |
0.9.8 | 1,670 | 6/10/2022 |
0.9.7 | 4,238 | 6/9/2022 |
0.9.6 | 4,227 | 6/5/2022 |
0.9.5 | 2,844 | 6/3/2022 |
0.9.3 | 4,135 | 6/3/2022 |
0.9.2 | 2,454 | 5/31/2022 |
0.9.1 | 2,409 | 5/31/2022 |
0.9.0 | 2,395 | 5/31/2022 |
0.8.3-beta.1 | 110 | 5/31/2022 |
0.8.2 | 1,715 | 5/30/2022 |
0.8.1 | 1,724 | 5/29/2022 |