spec
Specification
| spec | Specification | |
|---|---|---|
| 2 | 6 | |
| 2,991 | 1,799 | |
| 0.6% | - | |
| 0.0 | 6.7 | |
| 7 months ago | about 2 months ago | |
| C# | ||
| GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
spec
-
OAM for Non-Containerized Apps
OAM Spec
-
Open Application Model – An open standard for defining cloud native apps
The spec doesn't appear to address the 12-factor app spec which does a similar job in a more general way.
https://github.com/oam-dev/spec/search?q=12+factor
https://12factor.net/
Specification
-
Why doesn't eager loading work with EF?
If so, then look into this
-
What is the point of using repository pattern with entity framework
Also, to minimize duplication of code and optimize your architecture i suggest using something like https://github.com/ardalis/Specification
-
Linq with an expression not returning an IAsyncEnumerable
This is a great candidate project for the Ardalis.Specifications library.
-
Confused on how to structure my API with Entity Framework
This is honestly such an amazing way to make sure you have a clear view of what your Linq does, see https://github.com/ardalis/Specification - note that the examples on the front git page uses a repository, but he later allowed the use directly on DbSet which finally made it possible for me to use the library.
-
How do you handle querying large object graphs with EF Core (and other questions)?
Check out the specification pattern - it is designed to encapsulate query logic similar to your example. Steve Smith has a nice library for it on GitHub: https://github.com/ardalis/Specification
-
Using Dapper and EF Core in the same project. Is it a bad practice? Is there any uniform way to abstract them?
I'm thinking that the only way to abstract both of them would be to have the repositories return IEnumerables and have well defined aggregates for the entire application to avoid an exploding number of methods on the interface, but this is not possible in my project*. I've looked at Steve Smith's Specification library, but since it works with IQueryable, it would not work with Dapper.
What are some alternatives?
kubevela - The Modern Application Platform.
did-core - W3C Decentralized Identifier Specification v1.0
helm-zabbix - HELM package for deploying Zabbix to Kubernetes
data-interoperability-panel - Repository for the Solid Data Interoperability Panel
helm-zabbix - Helm chart for Zabbix
CleanArchitecture - Clean Architecture Solution Template: A starting point for Clean Architecture with ASP.NET Core
specification - Serverless Workflow Specification
Result - A result abstraction that can be mapped to HTTP response codes if needed.
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
examQuestionCore - Randomly distribute exam questions - server component written in C#/.NET5
realworlddotnet
GuardClauses - A simple package with guard clause extensions.