This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| using Marten.AsyncDaemon.Testing; | |
| using Marten.AsyncDaemon.Testing.TestingSupport; | |
| using Marten.Internal; | |
| using Marten.Internal.CompiledQueries; | |
| using Marten.Internal.Storage; | |
| using Marten.Linq; | |
| using Marten.Linq.QueryHandlers; | |
| using Marten.Schema; | |
| using Marten.Schema.Arguments; | |
| using Marten.Testing.Documents; |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| using System; | |
| using System.Collections.Generic; | |
| using Baseline; | |
| using Microsoft.Extensions.Logging; | |
| using StoryTeller.Results; | |
| using StoryTeller.Util; | |
| namespace Jasper.TestSupport.Storyteller.Logging | |
| { | |
| /// <summary> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| ============================================================================================================================================================= | |
| ServiceType Namespace Lifecycle Description Name | |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------- | |
| IContainer Lamar Scoped Current IContainer IContainer | |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------- | |
| IEngine Lamar.Testing.IoC.Diagnostics Transient new Hemi() The Hemi | |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| public class SqlSender_HomeEndpoint_post_one : Jasper.Http.Model.RouteHandler | |
| { | |
| private readonly SqlServerSettings _sqlServerSettings; | |
| private readonly IMessagingRoot _messagingRoot; | |
| public SqlSender_HomeEndpoint_post_one(SqlServerSettings sqlServerSettings, IMessagingRoot messagingRoot) | |
| { | |
| _sqlServerSettings = sqlServerSettings; | |
| _messagingRoot = messagingRoot; | |
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| What this benchmark does is bootstrap an ASP.Net Core system with MVC and AddLogging, | |
| then try to create every single registered type that is common between the two | |
| configurations. Throws out the initial run. | |
| Method | Mean | Error | StdDev | | |
| ------------- |----------:|---------:|---------:| | |
| StructureMap | 516.72 us | 4.310 us | 3.599 us | | |
| BlueMilk | 86.04 us | 1.214 us | 1.076 us | |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| public class RavenDBRepository<T, I> : IRepository<T, I> where T: IAggregateRoot<I> where I : struct, IIdentity<I> | |
| { | |
| private readonly IAsyncDocumentSession _session; | |
| public RavenDBRepository(IAsyncDocumentSession session) | |
| { | |
| _session = session; | |
| } | |
| public async Task<T> GetAsync(I identity) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| // Yes Dorothy, this is some circular reference action going on here. | |
| // We'll get it sorted out later |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| using System; | |
| using System.Security.Cryptography.X509Certificates; | |
| namespace BlueMilk.Tests | |
| { | |
| public class WorkItem | |
| { | |
| public DateTime Started { get; set; } | |
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| protected Upsert(object document) | |
| { | |
| // The first time I checked for "Document == null", so it threw | |
| // EVERY TIME | |
| if (document == null) throw new ArgumentNullException(nameof(document)); | |
| Document = document; | |
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Hey @all, happy New Year to everybody. I’m needing to get Storyteller 4 ready for our internal usage soon and I’m running out of steam, so I’ve pared back the goals for the 4.0 release. You can see everything I’m thinking for a release timeline in the Github milestones: https://github.com/storyteller/Storyteller/milestones | |
| What’s in: markdown persistence, the mechanism to define the fixture language in markdown, the step through mode, bug fixes, and CoreCLR/dotnet cli support | |
| I’m pushing off being able to export spec visualizations, more performance tracking, and spec tagging until 4.1 sometime around maybe the end of the 1st quarter. | |
| Any thoughts on any of this? Anybody willing to try out the 4.0 alpha in a couple weeks? | |
| And I’m definitely bailing out on specification parallelization until a 5.0 release later this year |