Jaunty Extensions

Documentation for Jaunty extension packages that build on top of Jaunty core.

Available Extensions

Jaunty.FlatFiles

Flat file support for Jaunty, enabling SQL queries on CSV, TSV, Parquet, JSON, and other file formats using DuckDB as the embedded query engine.

Documentation:

• flatfiles/README.md - FlatFiles overview
• flatfiles/architecture.md - Architecture and design
• flatfiles/code-analysis.md - Code analysis report

Key Features:

• Query flat files using SQL
• Support for CSV, TSV, Parquet, JSON, Excel, Delta Lake, Iceberg
• DuckDB embedded query engine
• Import/export to external databases
• Full CRUD operations on file data

Jaunty.Extensions.Reflection

Reflection-based entity mapping for scenarios where source generation is not available.

Documentation: Coming soon

Key Features:

• Runtime reflection mapping
• Compatible with NativeAOT (with manual initialization)
• Fallback for dynamic scenarios

Jaunty.Extensions.Logging

Microsoft.Extensions.Logging and dependency-injection integration. This package exists so that Jaunty core can declare no dependencies at all on net8.0 and net10.0; it carries Microsoft.Extensions.Logging.Abstractions and Microsoft.Extensions.DependencyInjection.Abstractions on its behalf.

Documentation: ../02-architecture/dependencies.md

Contains:

• LoggingInterceptor - logs SQL with level control, slow-query detection and parameter masking
• LoggingConfiguration - its options, including the sensitive-parameter list
• AddJauntyLogging, AddJauntyInterceptor<T>, ApplyJauntyInterceptors - IServiceCollection wiring

Namespaces are unchanged from when these types lived in core, so adopting it is a package reference and no source edits.

Extension Architecture

Extensions follow the same design principles as Jaunty core:

1. Minimal dependencies - an extension depends on Jaunty core and takes a package reference only where the feature is that dependency: Extensions.Logging exists to hold the Microsoft.Extensions packages, and FlatFiles.DuckDB cannot work without DuckDB. Everything else stays dependency-free on net8.0/net10.0. See ../02-architecture/dependencies.md for the full list.
2. Consistent API - Match Jaunty core patterns and naming
3. Performance-first - Optimized for minimal allocations
4. NativeAOT compatible - Support for AOT compilation scenarios

For Extension Developers

Design Guidelines

When creating new extensions for Jaunty:

1. Match core patterns - Use the same folder structure and naming conventions
2. Document thoroughly - Follow the documentation structure in this folder
3. Test extensively - Maintain high test coverage like core
4. Consider AOT - Design for NativeAOT compatibility from the start

Documentation Structure

04-extensions/
├── README.md                      # This file - extension overview
├── {extension-name}/
│   ├── README.md                  # Extension overview
│   ├── architecture.md            # Architecture documentation
│   ├── api-reference.md           # API documentation
│   └── code-analysis.md           # Code analysis (if applicable)

See Also