Giraffe
SQLProvider
Giraffe | SQLProvider | |
---|---|---|
19 | 9 | |
2,055 | 559 | |
0.8% | 0.9% | |
6.8 | 8.5 | |
21 days ago | 14 days ago | |
F# | F# | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
Giraffe
-
The combined power of F# and C#
Giraffe is another interesting one to explore: https://giraffe.wiki/
Giraffe is nice because it is itself built "just" as ASP.NET Core Middleware so it plays a bit more nicely than Suave with a mixed stack of C#-defined Middleware.
It's more likely you accidentally fall back into just translating C# patterns to non-idiomatic F# with Giraffe, but it's also nicer when in that case of needing to live in both worlds and use a mixture of libraries built for C# ASP.NET projects.
-
ASP.NET Core updates in .NET 8 Preview 4 - .NET Blog
There are also some F# frameworks built on top of ASP.NET core like https://giraffe.wiki
- Confusion in learning Giraffe's HttpHandler
-
Is there any advantage to using F# instead of C#?
If you have an interest in F#, I highly recommend diving in because (1) it has a ton of things you might learn to appreciate in C#; (2) it has things C# cannot have. I do like some of the suggestions people have made regarding mixing your code bases, but I'll also say that building, say, endpoint routing in Giraffe is (to repeat myself) easy, simple, and elegant.
-
Targeting Node, Bun and Deno With F#
Bix is a micro-framework designed with F# in mind and that runs on both Deno and Bun! and in theory it also should even run in a service worker! (intercepting fetch requests) although I haven't tested that yet, it offers a general purpose handler that coupled with a set of route definitions it can bring a Giraffe/Saturn like framework to life in JavaScript runtimes which is incredibly awesome! useful? maybe not š , but awesome indeed. Let's see some code for it
-
If you were to create a Web API today from scratch how would you do it ?
Backend: Most likely it would be a toss between https://saturnframework.org or https://giraffe.wiki. They both combins the extremely good type system in F# combined with the ease of a minimal API.
-
Is it possible to run C# asp.net core MVC and f# giraffe in a single solution
I was wondering if its possible to simultaneously run a C# core MVC project in combination with https://github.com/giraffe-fsharp/Giraffe
-
Overriding JSON serializer in Giraffe
By default Giraffe, the framework which I use as a web server, uses Newtonsoft.Json to serialize results to JSON. However, for discriminated union, it generates quite a lot of JSON so I've switched to System.Text.Json which is built into newer versions of .Net Core. In combination with FSharp.SystemTextJson package allows serializing discriminated unions more gracefully. All we need is to decorate Branch type with JsonFSharpConverter(JsonUnionEncoding.BareFieldlessTags) attribute.
-
Introducing Giraffe.Htmx
Giraffe is a library that sits atop ASP.NET Core and allows developers to build web applications in a functional style; dotnet new giraffe is literally my starting point when I begin a new web application project. (Rather than write three more sentences filled with effusive praise, Iāll just leave it at that; itās great.) It also provides a view engine (that builds upon Suaveās āexperimentalā view engine) which uses an F# DSL to define HTML in a strongly-typed way. It has been incredibly efficient for a while, but with .NETās work over the past two releases at improving performance, and Giraffeās adoption of those techniques, it is lightning fast.
-
Show HN: F# web server in 3-4 lines of code
Wrapping ASP.NET Core to be easier and more idiomatic with F# seems to be a common domain. Out of curiosity, did you look at any existing projects? If so, what was lacking from them that made you decide to write WebFrame?
Giraffe: https://github.com/giraffe-fsharp/Giraffe
SQLProvider
-
Warning FS0101: This API supports the FSharp.Data.SqlClient...
For completeness, there is also the SqlDataProvider, which I only tried out a little years ago, before composibility was baked in. Worth a look.
-
Is there a market for a complete fsharp ORM library?
Have you heard of type providers? https://fsprojects.github.io/SQLProvider/ I think this library might be what you are looking for
-
If you were to create a Web API today from scratch how would you do it ?
Database: SQL or Event Store. If SQL, One of https://fsprojects.github.io/SQLProvider/, https://github.com/Dzoukr/Dapper.FSharp or https://github.com/SQLStreamStore/SQLStreamStore
-
What's new in F# 6
One of the more popular Type Providers I used is the SQL Provider, but even it has severe limitations when it comes to .NET Core.
-
Fable is a compiler that brings F# into the JavaScript ecosystem
There was a wave of popularity in 2017 as well. I used to work on it full time back then, and enjoyed it a lot. The SQLProvider [0] and other type providers like it are super impressive!
[0] https://fsprojects.github.io/SQLProvider/
-
Weird
(1) F# Type Providers still blow my mind.
Strongly typed SQL/XML/CSV/JSON without boilerplate is a massive leap forward, and it's a shame that it hasn't caught on.
https://fsprojects.github.io/SQLProvider/#Example
-
EF vs Dapper - a false dilemma
Like this?
-
Getting SQL Provider to work with PostgreSQL
So... I'm a little bit lost here. I must say, I love this language, but documentation is definitely not its greatest strength. I've looked at the SQLProvider documentation and found no information. Then I looked through the repository issues and found a lot of people with similar issues and, even though they should theoretically be solved with version 1.2, I tried doing what ended up working for them, with little luck. I've tried different combinations of library targets and dependencies versions but none worked.
-
Structure of .NET Core open source F# projects
So when I clone a typical open source F# project from GitHub (e.g. SQLProvider, to pick a recent one that I wrestled with), I'm often at a loss how to build and debug the thing. I've figured out that running build.cmd is usually a good place to start, but then what? Can I still open the .sln in Visual Studio and build/debug it there?
What are some alternatives?
Suave.IO - Suave is a simple web development F# library providing a lightweight web server and a set of combinators to manipulate route flow and task composition.
Dapper - Dapper - a simple object mapper for .Net [Moved to: https://github.com/DapperLib/Dapper]
Saturn - Opinionated, web development framework for F# which implements the server-side, functional MVC pattern
Entity Framework - EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
Dapper.FastCRUD - fast & light .NET ORM for strongly typed people
Falco - A toolkit for building fast and functional-first web applications using F#.
LINQ to DB - Linq to database provider.
ASP.NET MVC
PetaPoco - Official PetaPoco, A tiny ORM-ish thing for your POCO's
Freya - Freya Web Stack - Meta-Package
EntityFramework.DatabaseMigrator - EntityFramework.DatabaseMigrator is a WinForms utility to help manage Entity Framework 6.0+ migrations.