Solid Instruments is a single-sourced, loosely-coupled collection of .NET libraries that help you rapidly fill feature gaps, overcome common and uncommon design challenges, and deliver stable, secure, high-performance software.
This issue represents a request for new Solid Instruments functionality.
Overview
RapidField.SolidInstruments.Core.Extensions.ByteCollectionExtensions utilizes a static HashAlgorithm. Hashing operations should initialize new HashAlgorithm instances.
Statement of work
The following list describes the work to be done and defines acceptance criteria for the feature.
All HashAlgoritm members in the software should be instance members or local variables.
This issue represents a request for documentation, testing, refactoring or other non-functional changes.
Overview
Issue a production release for v1.0.26-preview.
Statement of work
The following list describes the work to be done.
Update documentation and release notes to reflect changes.
Update appveyor.yml with new version number.
Submit a pull request against master.
Close and cleanup branches.
Revision control plan
Solid Instruments uses the RapidField Revision Control Workflow. Individual contributors should follow the branching plan below when working on this issue.
master is the pull request target for
release/v1.0.26-preview1, which is the pull request target for
This issue represents a request for new Solid Instruments functionality.
Overview
There is currently no native support for StructureMap using the inversion of control abstractions. A new library should be created which implements the inversion of control abstractions for StructureMap.
Statement of work
The following list describes the work to be done and defines acceptance criteria for the feature.
A new library named RapidField.SolidInstruments.InversionOfControl.StructureMap should be exposed which draws upon the RapidField.SolidInstruments.InversionOfControl abstractions.
The library should implement StructureMap analogs to the types exposed by RapidField.SolidInstruments.InversionOfControl.StructureMap.
Revision control plan
Solid Instruments uses the RapidField Revision Control Workflow. Individual contributors should follow the branching plan below when working on this issue.
master is the pull request target for
release/v1.1.0-preview1, which is the pull request target for
develop, which is the pull request target for
feature/00012-structuremap-support, which is the pull request target for contributing user branches, which should be named using the pattern
This issue represents a request for new Solid Instruments functionality.
Overview
MD5 is currently used by the byte collection extensions. While it is generally safe for checksum operations and it was included and advertised for such purposes, it should be replaced in favor of SHA256 to protect non-advanced users who may use it for cryptographic purposes.
Statement of work
The following list describes the work to be done and defines acceptance criteria for the feature.
MD5 should be replaced with SHA256.
256-bit digests should be folded to 128-bit where necessary.
This issue represents a request for new Solid Instruments functionality.
Overview
Using EnhancedReadabilityGuid often requires casting to and from System.Guid. An implicit cast operator should be added to improve consuming code cleanliness.
Statement of work
The following list describes the work to be done and defines acceptance criteria for the feature.
An implicit cast operator from EnhancedReadabilityGuid to Guid should be added.
This issue represents a request for documentation, testing, refactoring or other non-functional changes.
Overview
Replace the existing example projects with new projects that make use of recently-introduced abstractions and paradigms.
Statement of work
The following list describes the work to be done.
Create new domain model libraries.
Create new service applications.
Create new web applications.
Revision control plan
Solid Instruments uses the RapidField Revision Control Workflow. Individual contributors should follow the branching plan below when working on this issue.
master is the pull request target for
release/v1.1.0-preview1, which is the pull request target for
develop, which is the pull request target for
maintenance/00371-example-projects, which is the pull request target for contributing user branches, which should be named using the pattern
This issue represents a request for documentation, testing, refactoring or other non-functional changes.
Overview
The Governance Model document is currently a work-in-progress. It should be completed.
Statement of work
The following list describes the work to be done.
Complete the Governance Model document.
Revision control plan
Solid Instruments uses the RapidField Revision Control Workflow. Individual contributors should follow the branching plan below when working on this issue.
master is the pull request target for
release/v1.0.1-preview1, which is the pull request target for
develop, which is the pull request target for
maintenance/00290-governance-doc, which is the pull request target for contributing user branches, which should be named using the pattern
This issue represents a request for documentation, testing, refactoring or other non-functional changes.
Overview
Test coverage for the RapidField.SolidInstruments.Core.Concurrency.ConcurrencyControlToken class is low. Additional unit tests should be created to improve test coverage.
Statement of work
The following list describes the work to be done and defines acceptance criteria for the feature.
Author additional unit tests that improve coverage for the aforementioned class.
Revision control plan
Solid Instruments uses the RapidField Revision Control Workflow. Individual contributors should follow the branching plan below when working on this issue.
master is the pull request target for
release/v1.0.1-preview1, which is the pull request target for
develop, which is the pull request target for
maintenance/00200-concurrencycontroltoken-tests, which is the pull request target for contributing user branches, which should be named using the pattern
This issue represents a request for documentation, testing, refactoring or other non-functional changes.
Overview
The Solid Instrumentsdocumentation website is currently published using AppVeyor's native tooling. To avoid vendor lock-in, the documentation website publish process should not rely on a specific CI/CD service.
Statement of work
The following list describes the work to be done.
Develop source-controlled CI/CD scripting that publishes the compiled documentation website without relying on AppVeyor.
Modify the AppVeyor configuration to remove the existing FTP publish process.
Revision control plan
Solid Instruments uses the RapidField Revision Control Workflow. Individual contributors should follow the branching plan below when working on this issue.
master is the pull request target for
release/v1.0.26-preview1, which is the pull request target for
develop, which is the pull request target for
maintenance/00293-publish-docweb, which is the pull request target for contributing user branches, which should be named using the pattern
This issue represents a request for documentation, testing, refactoring or other non-functional changes.
Overview
Test coverage for the RapidField.SolidInstruments.SignalProcessing.ChannelCollection class is low. Additional unit tests should be created to improve test coverage.
Statement of work
The following list describes the work to be done.
Author additional unit tests that improve coverage for the aforementioned class.
Revision control plan
Solid Instruments uses the RapidField Revision Control Workflow. Individual contributors should follow the branching plan below when working on this issue.
master is the pull request target for
release/v1.0.1-preview1, which is the pull request target for
develop, which is the pull request target for
maintenance/00203-channelcollection-tests, which is the pull request target for contributing user branches, which should be named using the pattern
This issue represents a request for documentation, testing, refactoring or other non-functional changes.
Overview
The Architectural Guide document is currently a work-in-progress. It should be completed.
Statement of work
The following list describes the work to be done.
Complete the Architectural Guide document.
Revision control plan
Solid Instruments uses the RapidField Revision Control Workflow. Individual contributors should follow the branching plan below when working on this issue.
master is the pull request target for
release/v1.0.26-preview1, which is the pull request target for
develop, which is the pull request target for
maintenance/00291-architecture-doc, which is the pull request target for contributing user branches, which should be named using the pattern
This issue represents a request for the production release of a new version of Solid Instruments.
Overview
Issue a production software release for v1.0.26.
Statement of work
The following list describes the work to be done.
Update source documentation to reflect software changes.
Update documentation website to reflect software changes.
Add release notes with details that reflect software changes.
Update appveyor.yml to reflect new version number.
Submit a pull request against the master branch.
Close and destroy the completed working branches.
Revision control plan
Solid Instruments uses the RapidField Revision Control Workflow. Individual contributors should follow the branching plan below when working on this issue.
master is the pull request target for
release/v1.0.26, which is the pull request target for
The following list describes the work to be done and defines acceptance criteria for the feature.
Resolve the complex method.
Revision control plan
Solid Instruments uses the RapidField Revision Control Workflow. Individual contributors should follow the branching plan below when working on this issue.
master is the pull request target for
release/v1.0.25-preview1, which is the pull request target for
develop, which is the pull request target for
feature/0053_complex-string-extensions, which is the pull request target for contributing user branches, which should be named using the pattern
This issue represents a request for new Solid Instruments functionality.
Overview
There is currently no native support for RabbitMQ using the messaging abstractions. A new library should be created which implements the messaging abstractions for RabbitMQ.
Statement of work
The following list describes the work to be done and defines acceptance criteria for the feature.
A new library named RapidField.SolidInstruments.Messaging.RabbitMq should be exposed which draws upon the RapidField.SolidInstruments.Messaging abstractions.
The library should implement RabbitMQ analogs to the types exposed by RapidField.SolidInstruments.Messaging.AzureServiceBus.
Revision control plan
Solid Instruments uses the RapidField Revision Control Workflow. Individual contributors should follow the branching plan below when working on this issue.
master is the pull request target for
develop, which is the pull request target for
release/v1.0.25-preview1, which is the pull request target for
feature/0007-rabbitmq-support, which is the pull request target for contributing user branches, which should be named using the pattern
This issue represents a request for documentation, testing, refactoring or other non-functional changes.
Overview
Test coverage for the RapidField.SolidInstruments.Core.TimeOfDay class is low. Additional unit tests should be created to improve test coverage.
Statement of work
The following list describes the work to be done.
Author additional unit tests that improve coverage for the aforementioned class.
Revision control plan
Solid Instruments uses the RapidField Revision Control Workflow. Individual contributors should follow the branching plan below when working on this issue.
master is the pull request target for
release/v1.0.1-preview1, which is the pull request target for
develop, which is the pull request target for
maintenance/00202-timeofday-tests, which is the pull request target for contributing user branches, which should be named using the pattern
This issue represents a request for documentation, testing, refactoring or other non-functional changes.
Overview
The performance of several bit field copy operations can be improved by utilizing the Span<T> and Memory<T> primitives in place of Array.Copy and Buffer.BlockCopy. Those operations should be refactored to use the new primitives where appropriate.
Statement of work
The following list describes the work to be done.
Find and refactor uses of Array.Copy and Buffer.BlockCopy, where appropriate, to use the new primitives.
Revision control plan
Solid Instruments uses the RapidField Revision Control Workflow. Individual contributors should follow the branching plan below when working on this issue.
master is the pull request target for
release/v1.0.26-preview1, which is the pull request target for
develop, which is the pull request target for
maintenance/00289-refactor-copies, which is the pull request target for contributing user branches, which should be named using the pattern
The following list describes the work to be done and defines acceptance criteria for the feature.
Resolve the complex method.
Revision control plan
Solid Instruments uses the RapidField Revision Control Workflow. Individual contributors should follow the branching plan below when working on this issue.
master is the pull request target for
release/v1.0.25-preview1, which is the pull request target for
develop, which is the pull request target for
feature/0055_complex-rng-extensions, which is the pull request target for contributing user branches, which should be named using the pattern
This issue represents a request for documentation, testing, refactoring or other non-functional changes.
Overview
GitHub does not recognize the existing issue templates. The existing issue templates should be updated so that they are recognizable and usable by GitHub users.
Statement of work
The following list describes the work to be done and defines acceptance criteria for the feature.
Modify or recreate the existing GitHub issue templates so that they are usable by the GitHub software and, consequently, by GitHub users.
This issue represents a request for documentation, testing, refactoring or other non-functional changes.
Overview
Several Solid Instruments APIs use the await keyword unnecessarily. Those APIs should be refactored so avoid use of await.
Statement of work
The following list describes the work to be done.
Find and refactor the offending APIs.
Revision control plan
Solid Instruments uses the RapidField Revision Control Workflow. Individual contributors should follow the branching plan below when working on this issue.
master is the pull request target for
release/v1.0.26-preview1, which is the pull request target for
develop, which is the pull request target for
maintenance/00288-refactor-awaits, which is the pull request target for contributing user branches, which should be named using the pattern
This issue represents a request for documentation, testing, refactoring or other non-functional changes.
Overview
The Development Guidelines document is currently a work-in-progress. It should be completed.
Statement of work
The following list describes the work to be done.
Complete the Development Guidelines document.
Revision control plan
Solid Instruments uses the RapidField Revision Control Workflow. Individual contributors should follow the branching plan below when working on this issue.
master is the pull request target for
release/v1.0.1-preview1, which is the pull request target for
develop, which is the pull request target for
maintenance/00292-guidelines-doc, which is the pull request target for contributing user branches, which should be named using the pattern
This issue represents a suggestion for new Solid Instruments functionality.
Overview
Extend the Autofac and native .NET dependency injection abstractions to expose single-line registration options for Entity Framework support dependencies.
Statement of work
The following list describes the work to be done and defines acceptance criteria for the feature.
Create a new project named RapidField.SolidInstruments.DataAccess.Autofac.Ef.
Create a new project named RapidField.SolidInstruments.DataAccess.DotNetNative.Ef.
Create an aggregate dependency registration method for Entity Framework support via Autofac.
Create an aggregate dependency registration method for Entity Framework support via native .NET IoC.
Extend the documentation to cover the new components.
Additional information
Revision control plan
Solid Instruments uses the RapidField Revision Control Workflow. Individual contributors should follow the branching plan below when working on this issue.
master is the pull request target for
release/v1.0.26-preview1, which is the pull request target for
develop, which is the pull request target for
feature/000304-ef-registration, which is the pull request target for contributing user branches, which should be named using the pattern