Cratis.Fundamentals.Specs
6.0.2
Prefix Reserved
See the version list below for details.
dotnet add package Cratis.Fundamentals.Specs --version 6.0.2
NuGet\Install-Package Cratis.Fundamentals.Specs -Version 6.0.2
<PackageReference Include="Cratis.Fundamentals.Specs" Version="6.0.2" />
paket add Cratis.Fundamentals.Specs --version 6.0.2
#r "nuget: Cratis.Fundamentals.Specs, 6.0.2"
// Install Cratis.Fundamentals.Specs as a Cake Addin #addin nuget:?package=Cratis.Fundamentals.Specs&version=6.0.2 // Install Cratis.Fundamentals.Specs as a Cake Tool #tool nuget:?package=Cratis.Fundamentals.Specs&version=6.0.2
Fundamentals
Packages / Deployables
Builds
Description
The Cratis fundamentals holds generic reusable helpers, utilities and tools that aims at solving common problems and help developers be more productive. Fundamentals offers functionality for .NET and JavaScript environments. It is not a goal to have parity, as the different environments offer different building blocks.
You should look at it as a convenience layer on top of the existing base environment you're running in.
Read more about how to use it in our documentation.
Contributing
If you want to jump into building this repository and possibly contributing, please refer to contributing.
Prerequisites
The following are prerequisites to work with this repository.
Central Package Management
This repository leverages Central Package Management, which means that all package versions are managed from a file at the root level called Directory.Packages.props.
In addition there are also Directory.Build.props files for setting up common settings that are applied cross cuttingly.
Root package.json
The package.json
found at the root level defines all the workspaces. It is assumed
All developer dependencies are defined in the top level package.json
. The reason for this is to be able to provide global scripts
for every package to use for easier maintenance.
The package.json
found at the top level contains scripts that can then be used in a child project for this to work properly.
In a package, all you need to do is to define the scripts to use the global scripts in the `package.json´ of that project:
{
"scripts": {
"prepublish": "yarn g:build",
"clean": "yarn g:clean",
"build": "yarn g:build",
"lint": "yarn g:lint",
"lint:ci": "yarn g:lint:ci",
"test": "yarn g:test",
"ci": "yarn g:ci",
"up": "yarn g:up"
}
}
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net8.0 is compatible. 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. net9.0 is compatible. |
-
net8.0
- Cratis.Fundamentals (>= 6.0.2)
- Cratis.Specifications.XUnit (>= 3.0.4)
- Microsoft.NET.Test.Sdk (>= 17.11.1)
- moq (>= 4.20.72)
- xunit (>= 2.9.2)
- xunit.runner.visualstudio (>= 2.8.2)
-
net9.0
- Cratis.Fundamentals (>= 6.0.2)
- Cratis.Specifications.XUnit (>= 3.0.4)
- Microsoft.NET.Test.Sdk (>= 17.11.1)
- moq (>= 4.20.72)
- xunit (>= 2.9.2)
- xunit.runner.visualstudio (>= 2.8.2)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.