SimpleDateTimeProvider
A simple abstraction over C#'s DateTime.Now, DateTime.Today and DateTime.UtcNow so you can control these values in your tests. No longer do you have to attempt shenanigans in your tests to handle when you need to use those values in your code. (by stphnwlsh)
GraphQL for .NET
GraphQL for .NET (by graphql-dotnet)
SimpleDateTimeProvider | GraphQL for .NET | |
---|---|---|
1 | 6 | |
9 | 5,742 | |
- | 0.3% | |
6.0 | 9.0 | |
about 1 month ago | 17 days ago | |
C# | C# | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
SimpleDateTimeProvider
Posts with mentions or reviews of SimpleDateTimeProvider.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-11-27.
GraphQL for .NET
Posts with mentions or reviews of GraphQL for .NET.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-13.
-
Redis as a Database — Live Data Updates with PubSub and GraphQL Subscriptions
The way that’s done in Visualizer is quite specific to my needs and to the library that I’m using, called GraphQl-Dotnet.
-
Graphql-dotnet vs Hot Chocolate, which one to choose?
I'm starting a brand new project. Looks like if we want to do GraphQL in .NET, it's either graphql-dotnet or Hot Chocolate. Both look pretty good on paper.
-
Dotnet Outdated - Install and Update
This is a template API using Clean Architecture alongside a .net implementation of GraphQL.
-
Improving the GraphQL.NET Data Loader Execution Strategy
Customising the default ParallelExecutionStrategy is harder though. The best way to achieve this is to take the existing source code and modify it. The key section we need to modify is the last part of the try/catch in ExecuteNodeTreeAsync:
-
when will we see a native Date/Time type?
Because it can depend on the context. I know the PHP Laravel integration for GraphQL I used was leveraging the Carbon interface instead of PHP's native Date type. In NestJS the integrated solution allows you to choose whether to use UNIX timestamps or ISO datetimes. TypeGraphQL does something similar if I'm not wrong, and the .NET library added a bunch of date-related scalars in a PR they made for v2.
-
Learn GraphQL + React in 30 mins with Apollo's new learning platform Odyssey!
If you're loving your current stack, you should stick with it :) But, if you're experiencing some of the problems described in the article, you might want to try Apollo. It's incrementally adoptable, so you don't have to rewrite your whole app to start using it. There's also a community maintained .NET implementation of GraphQL, so you could use that for your graph and use Apollo Client to connect it to the frontend.