ApiEndpoints
fslang-suggestions
ApiEndpoints | fslang-suggestions | |
---|---|---|
22 | 43 | |
2,992 | 338 | |
- | 0.3% | |
4.3 | 2.8 | |
about 1 month ago | 9 months ago | |
C# | ||
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.
ApiEndpoints
- Web apis with controllers but whats the other way
-
Does anyone like minimal API?
I personally prefer the API Endponts project that doesn’t get the love it deserves. It’s really the best of both worlds. It breaks each endpoint up into one file to make it easier to manage and prevents ginormous Controllers.
-
Are minimal APIs meant to be used for lightweight projects or do they offer something controllers don't?
I personally think it feels "cleaner" when using the controllers instead because they provide more out of the box features. Having one endpoint per file is a nice thing so I'm thinking about using the ApiEndpoints ( https://github.com/ardalis/ApiEndpoints ) package.
-
Need help for refactoring my Controller
You can follow a "controller per endpoint" strategy. One good way to do it is with Steve Smith ApiEndpoints: https://github.com/ardalis/ApiEndpoints
- Need help understanding the purpose of MediatR in vertical slices architecture.
-
Thick or thin API controllers?
I'm not disputing the benefits of thin controllers but there are other ways to make the controllers thinner. For example, I could use libraries such as ApiEndpoints which allows me to have one handler class per REST endpoint. Basically, MediatR pattern but at the ASP.net level.
The only think I would suggest is to break endpoints into separate files via smth like this https://github.com/ardalis/ApiEndpoints
-
FastEndpoints v3.0 released with easy api versioning support!
You really should compare against https://github.com/ardalis/ApiEndpoints
-
FastEndpoints alternatives - ApiEndpoints and Carter
3 projects | 20 Jan 2022
- ASP.NET Core 6: Autenticación JWT y Identity Core
fslang-suggestions
-
Reusing static constraints with multiple generics
Trying to extend this https://github.com/fsharp/fslang-suggestions/issues/1089 to have two generics:
-
VN Compiler. How to use Blazor components with Bolero. Introducing Blazor.Diagrams. (Pt. 1) (Restart)
Basically, what I've made in Spiral. There is even a F# issue to improve the syntax.
-
Can I call method on the output of the pipe?
Not currently supported but it's an open language suggestion that's likely to end up in F#. https://github.com/fsharp/fslang-suggestions/issues/506
- Mapperly - A .NET source generator for object to object mappings
-
Microfeatures I'd like to see in more languages
Re: the argument accessor shorthand, there seems to be a proposal for exactly that (using _ instead of &): https://github.com/fsharp/fslang-suggestions/issues/506#issu...
-
Need help with Azure.Storage.Blobs to do simple enumerate blob items
I found this post (https://github.com/fsharp/fslang-suggestions/issues/975) which is about the same thing, but I'm confused as to what the final resolution was. There was mention of a taskSeq, but I can't find much info on that.
-
OCaml programmer with some noob F# ecosystem questions
An issue in FSharp suggestions
-
Announcing .NET 7 Preview 7
F# doesn’t currently seem to support source generators.
-
What are the features you're looking forward to in the next version of Fsharp?
"Blessed" literals: only FSharp.List and System.Array have a built-in collection syntax in the language ([ ] and [| |]). Only FSharp.List has a special pattern matching constructor (::). The language itself shouldn't favor a particular type over another: it should be possible, at the library level, to write the same code but using different collection types (related discussion here).
-
F# (in)compatibility
I mostly write F# so I can only speak for F#, but if you want you can create a module which extends Seq to add the OCaml names. I suspect the same is possible in OCaml. The authors are not trying to impede compatibility, but compatibility is not a goal. If you value compatibility, or adhering to ML norms, and you use F#, I recommend you (kindly) advocate for it in relevant issues on the F# language discussion repo. https://github.com/fsharp/fslang-suggestions/issues
What are some alternatives?
FastEndpoints - A light-weight REST API development framework for ASP.NET 6 and newer.
ProjectReunion - The Windows App SDK empowers all Windows desktop apps with modern Windows UI, APIs, and platform features, including back-compat support, shipped via NuGet.
FastEndpoints - A light-weight REST API development framework for ASP.Net 6 and newer. [Moved to: https://github.com/FastEndpoints/Library]
HVM - A massively parallel, optimal functional runtime in Rust
MediatR - Simple, unambitious mediator implementation in .NET
nand2tetris - Original course HDL solutions, F# implementations for the software stack, and VHDL implementations for the hardware stack for the nand2tetris course and The Elements of Computing Systems book.
IdentityServer4 - OpenID Connect and OAuth 2.0 Framework for ASP.NET Core
fslang-design - RFCs and docs related to the F# language design process, see https://github.com/fsharp/fslang-suggestions to submit ideas
Carter - Carter is framework that is a thin layer of extension methods and functionality over ASP.NET Core allowing code to be more explicit and most importantly more enjoyable.
FSharpPlus - Extensions for F#
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
ZIO - ZIO — A type-safe, composable library for async and concurrent programming in Scala