Feliz
SQLProvider
Our great sponsors
Feliz | SQLProvider | |
---|---|---|
20 | 9 | |
521 | 558 | |
- | 1.8% | |
6.1 | 8.4 | |
25 days ago | 10 days ago | |
F# | F# | |
MIT License | 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.
Feliz
-
Exploring a foreign F# codebase
NOTE: You can try this with the Feliz codebase, which is larger and has multiple .fsproj files. But as you will find out, the project structure is laid out just like we've seen here.
-
What do people use for REST APIs and Web Development now?
Feliz to create react apps, the most mature option.
-
F(#)ront-end Experience like Re-Frame (clojure(script))?
The Feliz DSL https://zaid-ajaj.github.io/Feliz/ looks fairly similar to Reagent or there's Fable.Lit https://fable.io/Fable.Lit/ which is more like jsx in that you write the html directly, adding active components via interpolated string mechanisms. There is a VS Code add in that gives you html+css syntax highlighting and auto complete inside your F# files.
-
OCaml programmer with some noob F# ecosystem questions
Feliz is a DSL for React, and paired with Vite give a hot reload experience that's close to the same as JS/TS, even the React dev tools work fine. Nobody has a ready to go package/template up right now but there's little stopping you from creating a NextJS app.
-
"redesign" of my Terminal.Gui.Elmish Project
It means it's similar to the Feliz DSL used to build React web apps: https://zaid-ajaj.github.io/Feliz/
-
Exploring The F# Frontend Landscape
Feliz
- A fresh retake of the React API in Fable
-
Minimalistic fluent api in C# to create complex reactive Avalonia applications
I'm curious to see how this goes, F# seems to excel at these type of DSL's (e.g. Feliz, a react DSL is a joy), a big part thanks to type inference and list comprehensions which are a game changer for that pesky conditional rendering.
-
F# and WebAssembly
if you've ever used Feliz or Avalonia.FuncUI then this DSL will make you feel at home, it's less verbose than the original DSL and gives you basically the same benefits, in the case of Fun.Blazor is slightly less performant but it is a viable alternative
-
Fable is a compiler that brings F# into the JavaScript ecosystem
Along with Fable highly recommend a look at Feliz. A joy to work with and its ViewEngine can also be separately used w/ Giraffe if you enjoy the syntax:
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!
-
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.
-
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?
fable-react - Fable bindings and helpers for React and React Native
Dapper - Dapper - a simple object mapper for .Net [Moved to: https://github.com/DapperLib/Dapper]
elmish - Elm-like abstractions for F# apps
Entity Framework - EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.
Fable: F# |> BABEL - F# to JavaScript, TypeScript, Python, Rust and Dart Compiler
Dapper.FastCRUD - fast & light .NET ORM for strongly typed people
Fable.Lit - Write Fable Elmish apps with Lit
LINQ to DB - Linq to database provider.
awesome-fable-react-native - An awesome list about to use Fable with ReactNative 🧚♀️
EntityFramework.DatabaseMigrator - EntityFramework.DatabaseMigrator is a WinForms utility to help manage Entity Framework 6.0+ migrations.
Sutil - Lightweight front-end framework for F# / Fable. No dependencies.
PetaPoco - Official PetaPoco, A tiny ORM-ish thing for your POCO's