Skip to content

Instantly share code, notes, and snippets.

@joe-oli
Created September 8, 2026 06:00
Show Gist options
  • Select an option

  • Save joe-oli/c456735493453179f7ae2214350087ba to your computer and use it in GitHub Desktop.

Select an option

Save joe-oli/c456735493453179f7ae2214350087ba to your computer and use it in GitHub Desktop.
Ideation prompt

Q. I don't like GitHub gists interface, it's good as a storage area but search, display is hit and miss, so i thought of designing my curated interface and at the same time learn its api. Let's plan.

A.

Q.

A.

Q.

A.

Preferred Toolset

Frontend

  • React / TypeScript / Vite
  • Bootstrap.css or react-bootstrap for global styling
  • CSS Modules for local/component-level overrides

Backend

  • .NET 10 (Controller-based only - no minimal APIs), OR
  • Node / Express with TypeScript

.NET Project Structure

  • Generated EF classes live in a dedicated layer project (e.g. Jolisoft.Demo.EFLayer)
  • The Web API project (e.g. Jolisoft.Demo.API) owns controllers, middleware, DTOs, and application services
  • Do not hand-edit generated EF files - regenerate whenever the schema changes
  • Use Data Annotations during EF scaffolding to keep fluent-api noise minimal

Database Strategy

  • Database-first: EF classes generated from DB schema, no code-first, no migrations
    • Applies to server-owned DBs: SQL Server Express, MariaDB, PostgreSQL
  • Exception - React Native + SQLite: use code-first migrations instead
    • Reason: on-device SQLite is owned by the shipped app, not an external DBA-managed source; migrations let schema changes apply incrementally to a device's existing local data, which database-first scaffolding has no mechanism for

Databases

  • MariaDB, PostgreSQL, SQL Server Express (free), SQLite - use whichever fits the project
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment