SQLProvider
Fable.Lit
SQLProvider | Fable.Lit | |
---|---|---|
9 | 9 | |
558 | 83 | |
0.7% | - | |
8.5 | 0.0 | |
12 days ago | about 1 year ago | |
F# | F# | |
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.
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?
Fable.Lit
-
How do I understand the build system in modern F# web projects?
The other major frameworks I use are tailwindcss for styling and Fable.Lit for the views.
-
What do people use for REST APIs and Web Development now?
Lit for Lit components.
- [Presentation] Fable.Lit
-
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.
-
Exploring The F# Frontend Landscape
This is my personal favorite one when it comes to Fable options, Fable.Lit builds on top of lit.dev which is a web component library built on web standards. It brings performant straightforward and inter-framework compatible components to the F# FE landscape since Lit works with DOM elements themselves rather than abstractions you can manipulate component instances like if you were doing vanilla JavaScript except that you can use the F# safety for that.
-
Building a Webpack alternative in F#
Around September vite got traction with the vue user base and other users as well. I also studied a bit the vite source code, and even used it for some Fable material for posts. I was trying to make some awareness of Fable.Lit support for Web Components and I wanted to experiment in reality how good vite was, and boi it's awesome If you're starting new projects that depend on node tooling in my opinion, it's your best bet.
-
Fable is a compiler that brings F# into the JavaScript ecosystem
I don't know a ton about Fable, but they recently wrapped Google's Lit to allow building functional templating and web components in it: https://fable.io/Fable.Lit/
Seems like a neat project.
-
Creating Web Components with Fable.Lit
Try Lit.Fable today!
-
Using lit-html with F#
Check the fable.lit github repository to see also ways to interact with inter-operate Lit + React within Fable!
What are some alternatives?
Dapper - Dapper - a simple object mapper for .Net [Moved to: https://github.com/DapperLib/Dapper]
vite - Next generation frontend tooling. It's fast!
Entity Framework - EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.
Feliz - A fresh retake of the React API in Fable and a collection of high-quality components to build React applications in F#, optimized for happiness
Dapper.FastCRUD - fast & light .NET ORM for strongly typed people
fast - The adaptive interface system for modern web experiences.
LINQ to DB - Linq to database provider.
Fable: F# |> BABEL - F# to JavaScript, TypeScript, Python, Rust and Dart Compiler
EntityFramework.DatabaseMigrator - EntityFramework.DatabaseMigrator is a WinForms utility to help manage Entity Framework 6.0+ migrations.
React - The library for web and native user interfaces.
PetaPoco - Official PetaPoco, A tiny ORM-ish thing for your POCO's
fable-react - Fable bindings and helpers for React and React Native