| .vscode | ||
| bin | ||
| cmd/testserver | ||
| internal | ||
| pkg | ||
| resolvespec-js | ||
| resolvespec-python | ||
| tests | ||
| .gitignore | ||
| generated_slogan.webp | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| make_release.sh | ||
| MIGRATION_GUIDE.md | ||
| openapi.yaml | ||
| README.md | ||
| todo.md | ||
📜 ResolveSpec 📜
ResolveSpec is a flexible and powerful REST API specification and implementation that provides GraphQL-like capabilities while maintaining REST simplicity. It offers two complementary approaches:
- ResolveSpec - Body-based API with JSON request options
- RestHeadSpec - Header-based API where query options are passed via HTTP headers
Both share the same core architecture and provide dynamic data querying, relationship preloading, and complex filtering.
🆕 New in v2.0: Database-agnostic architecture with support for GORM, Bun, and other ORMs. Router-flexible design works with Gorilla Mux, Gin, Echo, and more.
🆕 New in v2.1: RestHeadSpec (HeaderSpec) - Header-based REST API with lifecycle hooks, cursor pagination, and advanced filtering.
Table of Contents
- Features
- Installation
- Quick Start
- Migration from v1.x
- Architecture
- API Structure
- RestHeadSpec: Header-Based API
- Example Usage
- Testing
- What's New in v2.0
Features
Core Features
- Dynamic Data Querying: Select specific columns and relationships to return
- Relationship Preloading: Load related entities with custom column selection and filters
- Complex Filtering: Apply multiple filters with various operators
- Sorting: Multi-column sort support
- Pagination: Built-in limit/offset and cursor-based pagination
- Computed Columns: Define virtual columns for complex calculations
- Custom Operators: Add custom SQL conditions when needed
Architecture (v2.0+)
- 🆕 Database Agnostic: Works with GORM, Bun, or any database layer through adapters
- 🆕 Router Flexible: Integrates with Gorilla Mux, Gin, Echo, or custom routers
- 🆕 Backward Compatible: Existing code works without changes
- 🆕 Better Testing: Mockable interfaces for easy unit testing
RestHeadSpec (v2.1+)
- 🆕 Header-Based API: All query options passed via HTTP headers instead of request body
- 🆕 Lifecycle Hooks: Before/after hooks for create, read, update, and delete operations
- 🆕 Cursor Pagination: Efficient cursor-based pagination with complex sort support
- 🆕 Multiple Response Formats: Simple, detailed, and Syncfusion-compatible formats
- 🆕 Advanced Filtering: Field filters, search operators, AND/OR logic, and custom SQL
- 🆕 Base64 Encoding: Support for base64-encoded header values
API Structure
URL Patterns
/[schema]/[table_or_entity]/[id]
/[schema]/[table_or_entity]
/[schema]/[function]
/[schema]/[virtual]
Request Format
{
"operation": "read|create|update|delete",
"data": {
// For create/update operations
},
"options": {
"preload": [...],
"columns": [...],
"filters": [...],
"sort": [...],
"limit": number,
"offset": number,
"customOperators": [...],
"computedColumns": [...]
}
}
RestHeadSpec: Header-Based API
RestHeadSpec provides an alternative REST API approach where all query options are passed via HTTP headers instead of the request body. This provides cleaner separation between data and metadata.
Quick Example
GET /public/users HTTP/1.1
Host: api.example.com
X-Select-Fields: id,name,email,department_id
X-Preload: department:id,name
X-FieldFilter-Status: active
X-SearchOp-Gte-Age: 18
X-Sort: -created_at,+name
X-Limit: 50
X-DetailApi: true
Setup with GORM
import "github.com/bitechdev/ResolveSpec/pkg/restheadspec"
import "github.com/gorilla/mux"
// Create handler
handler := restheadspec.NewHandlerWithGORM(db)
// Register models using schema.table format
handler.Registry.RegisterModel("public.users", &User{})
handler.Registry.RegisterModel("public.posts", &Post{})
// Setup routes
router := mux.NewRouter()
restheadspec.SetupMuxRoutes(router, handler)
// Start server
http.ListenAndServe(":8080", router)
Setup with Bun ORM
import "github.com/bitechdev/ResolveSpec/pkg/restheadspec"
import "github.com/uptrace/bun"
// Create handler with Bun
handler := restheadspec.NewHandlerWithBun(bunDB)
// Register models
handler.Registry.RegisterModel("public.users", &User{})
// Setup routes (same as GORM)
router := mux.NewRouter()
restheadspec.SetupMuxRoutes(router, handler)
Common Headers
| Header | Description | Example |
|---|---|---|
X-Select-Fields |
Columns to include | id,name,email |
X-Not-Select-Fields |
Columns to exclude | password,internal_notes |
X-FieldFilter-{col} |
Exact match filter | X-FieldFilter-Status: active |
X-SearchFilter-{col} |
Fuzzy search (ILIKE) | X-SearchFilter-Name: john |
X-SearchOp-{op}-{col} |
Filter with operator | X-SearchOp-Gte-Age: 18 |
X-Preload |
Preload relations | posts:id,title |
X-Sort |
Sort columns | -created_at,+name |
X-Limit |
Limit results | 50 |
X-Offset |
Offset for pagination | 100 |
X-Clean-JSON |
Remove null/empty fields | true |
Available Operators: eq, neq, gt, gte, lt, lte, contains, startswith, endswith, between, betweeninclusive, in, empty, notempty
For complete header documentation, see pkg/restheadspec/HEADERS.md.
Lifecycle Hooks
RestHeadSpec supports lifecycle hooks for all CRUD operations:
import "github.com/bitechdev/ResolveSpec/pkg/restheadspec"
// Create handler
handler := restheadspec.NewHandlerWithGORM(db)
// Register a before-read hook (e.g., for authorization)
handler.Hooks.Register(restheadspec.BeforeRead, func(ctx *restheadspec.HookContext) error {
// Check permissions
if !userHasPermission(ctx.Context, ctx.Entity) {
return fmt.Errorf("unauthorized access to %s", ctx.Entity)
}
// Modify query options
ctx.Options.Limit = ptr(100) // Enforce max limit
return nil
})
// Register an after-read hook (e.g., for data transformation)
handler.Hooks.Register(restheadspec.AfterRead, func(ctx *restheadspec.HookContext) error {
// Transform or filter results
if users, ok := ctx.Result.([]User); ok {
for i := range users {
users[i].Email = maskEmail(users[i].Email)
}
}
return nil
})
// Register a before-create hook (e.g., for validation)
handler.Hooks.Register(restheadspec.BeforeCreate, func(ctx *restheadspec.HookContext) error {
// Validate data
if user, ok := ctx.Data.(*User); ok {
if user.Email == "" {
return fmt.Errorf("email is required")
}
// Add timestamps
user.CreatedAt = time.Now()
}
return nil
})
Available Hook Types:
BeforeRead,AfterReadBeforeCreate,AfterCreateBeforeUpdate,AfterUpdateBeforeDelete,AfterDelete
HookContext provides:
Context: Request contextHandler: Access to handler, database, and registrySchema,Entity,TableName: Request infoModel: The registered model typeOptions: Parsed request options (filters, sorting, etc.)ID: Record ID (for single-record operations)Data: Request data (for create/update)Result: Operation result (for after hooks)Writer: Response writer (allows hooks to modify response)
Cursor Pagination
RestHeadSpec supports efficient cursor-based pagination for large datasets:
GET /public/posts HTTP/1.1
X-Sort: -created_at,+id
X-Limit: 50
X-Cursor-Forward: <cursor_token>
How it works:
- First request returns results + cursor token in response
- Subsequent requests use
X-Cursor-ForwardorX-Cursor-Backward - Cursor maintains consistent ordering even with data changes
- Supports complex multi-column sorting
Benefits over offset pagination:
- Consistent results when data changes
- Better performance for large offsets
- Prevents "skipped" or duplicate records
- Works with complex sort expressions
Example with hooks:
// Enable cursor pagination in a hook
handler.Hooks.Register(restheadspec.BeforeRead, func(ctx *restheadspec.HookContext) error {
// For large tables, enforce cursor pagination
if ctx.Entity == "posts" && ctx.Options.Offset != nil && *ctx.Options.Offset > 1000 {
return fmt.Errorf("use cursor pagination for large offsets")
}
return nil
})
Response Formats
RestHeadSpec supports multiple response formats:
1. Simple Format (X-SimpleApi: true):
[
{ "id": 1, "name": "John" },
{ "id": 2, "name": "Jane" }
]
2. Detail Format (X-DetailApi: true, default):
{
"success": true,
"data": [...],
"metadata": {
"total": 100,
"filtered": 100,
"limit": 50,
"offset": 0
}
}
3. Syncfusion Format (X-Syncfusion: true):
{
"result": [...],
"count": 100
}
Example Usage
Reading Data with Related Entities
POST /core/users
{
"operation": "read",
"options": {
"columns": ["id", "name", "email"],
"preload": [
{
"relation": "posts",
"columns": ["id", "title"],
"filters": [
{
"column": "status",
"operator": "eq",
"value": "published"
}
]
}
],
"filters": [
{
"column": "active",
"operator": "eq",
"value": true
}
],
"sort": [
{
"column": "created_at",
"direction": "desc"
}
],
"limit": 10,
"offset": 0
}
}
Installation
go get github.com/bitechdev/ResolveSpec
Quick Start
ResolveSpec (Body-Based API)
ResolveSpec uses JSON request bodies to specify query options:
import "github.com/bitechdev/ResolveSpec/pkg/resolvespec"
// Create handler
handler := resolvespec.NewAPIHandler(gormDB)
handler.RegisterModel("core", "users", &User{})
// Setup routes
router := mux.NewRouter()
resolvespec.SetupRoutes(router, handler)
// Client makes POST request with body:
// POST /core/users
// {
// "operation": "read",
// "options": {
// "columns": ["id", "name", "email"],
// "filters": [{"column": "status", "operator": "eq", "value": "active"}],
// "limit": 10
// }
// }
RestHeadSpec (Header-Based API)
RestHeadSpec uses HTTP headers for query options instead of request body:
import "github.com/bitechdev/ResolveSpec/pkg/restheadspec"
// Create handler with GORM
handler := restheadspec.NewHandlerWithGORM(db)
// Register models (schema.table format)
handler.Registry.RegisterModel("public.users", &User{})
handler.Registry.RegisterModel("public.posts", &Post{})
// Setup routes with Mux
muxRouter := mux.NewRouter()
restheadspec.SetupMuxRoutes(muxRouter, handler)
// Client makes GET request with headers:
// GET /public/users
// X-Select-Fields: id,name,email
// X-FieldFilter-Status: active
// X-Limit: 10
// X-Sort: -created_at
// X-Preload: posts:id,title
See RestHeadSpec: Header-Based API for complete header documentation.
Option 1: Existing Code (Backward Compatible)
Your existing code continues to work without any changes:
import "github.com/bitechdev/ResolveSpec/pkg/resolvespec"
// This still works exactly as before
handler := resolvespec.NewAPIHandler(gormDB)
handler.RegisterModel("core", "users", &User{})
Migration from v1.x
ResolveSpec v2.0 introduces a new database and router abstraction layer while maintaining 100% backward compatibility. Your existing code will continue to work without any changes.
Repository Path Migration
IMPORTANT: The repository has moved from github.com/Warky-Devs/ResolveSpec to github.com/bitechdev/ResolveSpec.
To update your imports:
# Update go.mod
go mod edit -replace github.com/Warky-Devs/ResolveSpec=github.com/bitechdev/ResolveSpec@latest
go mod tidy
# Or update imports manually in your code
# Old: import "github.com/Warky-Devs/ResolveSpec/pkg/resolvespec"
# New: import "github.com/bitechdev/ResolveSpec/pkg/resolvespec"
Alternatively, use find and replace in your project:
find . -type f -name "*.go" -exec sed -i 's|github.com/Warky-Devs/ResolveSpec|github.com/bitechdev/ResolveSpec|g' {} +
go mod tidy
Migration Timeline
- Phase 1: Update repository path (see above)
- Phase 2: Continue using existing API (no changes needed)
- Phase 3: Gradually adopt new constructors when convenient
- Phase 4: Switch to interface-based approach for new features
- Phase 5: Optionally switch database backends or try RestHeadSpec
Detailed Migration Guide
For detailed migration instructions, examples, and best practices, see MIGRATION_GUIDE.md.
Architecture
Two Complementary APIs
┌─────────────────────────────────────────────────────┐
│ ResolveSpec Framework │
├─────────────────────┬───────────────────────────────┤
│ ResolveSpec │ RestHeadSpec │
│ (Body-based) │ (Header-based) │
├─────────────────────┴───────────────────────────────┤
│ Common Core Components │
│ • Model Registry • Filters • Preloading │
│ • Sorting • Pagination • Type System │
└──────────────────────┬──────────────────────────────┘
↓
┌──────────────────────────────┐
│ Database Abstraction │
│ [GORM] [Bun] [Custom] │
└──────────────────────────────┘
Database Abstraction Layer
Your Application Code
↓
Handler (Business Logic)
↓
[Hooks & Middleware] (RestHeadSpec only)
↓
Database Interface
↓
[GormAdapter] [BunAdapter] [CustomAdapter]
↓ ↓ ↓
[GORM] [Bun] [Your ORM]
Supported Database Layers
- GORM (default, fully supported)
- Bun (ready to use, included in dependencies)
- Custom ORMs (implement the
Databaseinterface)
Supported Routers
- Gorilla Mux (built-in support with
SetupRoutes()) - BunRouter (built-in support with
SetupBunRouterWithResolveSpec()) - Gin (manual integration, see examples above)
- Echo (manual integration, see examples above)
- Custom Routers (implement request/response adapters)
Option 2: New Database-Agnostic API
With GORM (Recommended Migration Path)
import "github.com/bitechdev/ResolveSpec/pkg/resolvespec"
// Create database adapter
dbAdapter := resolvespec.NewGormAdapter(gormDB)
// Create model registry
registry := resolvespec.NewModelRegistry()
registry.RegisterModel("core.users", &User{})
registry.RegisterModel("core.posts", &Post{})
// Create handler
handler := resolvespec.NewHandler(dbAdapter, registry)
With Bun ORM
import "github.com/bitechdev/ResolveSpec/pkg/resolvespec"
import "github.com/uptrace/bun"
// Create Bun adapter (Bun dependency already included)
dbAdapter := resolvespec.NewBunAdapter(bunDB)
// Rest is identical to GORM
registry := resolvespec.NewModelRegistry()
handler := resolvespec.NewHandler(dbAdapter, registry)
Router Integration
Gorilla Mux (Built-in Support)
import "github.com/gorilla/mux"
// Backward compatible way
router := mux.NewRouter()
resolvespec.SetupRoutes(router, handler)
// Or manually:
router.HandleFunc("/{schema}/{entity}", func(w http.ResponseWriter, r *http.Request) {
vars := mux.Vars(r)
handler.Handle(w, r, vars)
}).Methods("POST")
Gin (Custom Integration)
import "github.com/gin-gonic/gin"
func setupGin(handler *resolvespec.Handler) *gin.Engine {
r := gin.Default()
r.POST("/:schema/:entity", func(c *gin.Context) {
params := map[string]string{
"schema": c.Param("schema"),
"entity": c.Param("entity"),
}
// Use new adapter interfaces
reqAdapter := resolvespec.NewHTTPRequest(c.Request)
respAdapter := resolvespec.NewHTTPResponseWriter(c.Writer)
handler.Handle(respAdapter, reqAdapter, params)
})
return r
}
Echo (Custom Integration)
import "github.com/labstack/echo/v4"
func setupEcho(handler *resolvespec.Handler) *echo.Echo {
e := echo.New()
e.POST("/:schema/:entity", func(c echo.Context) error {
params := map[string]string{
"schema": c.Param("schema"),
"entity": c.Param("entity"),
}
reqAdapter := resolvespec.NewHTTPRequest(c.Request())
respAdapter := resolvespec.NewHTTPResponseWriter(c.Response().Writer)
handler.Handle(respAdapter, reqAdapter, params)
return nil
})
return e
}
BunRouter (Built-in Support)
import "github.com/uptrace/bunrouter"
// Simple setup with built-in function
func setupBunRouter(handler *resolvespec.APIHandlerCompat) *bunrouter.Router {
router := bunrouter.New()
resolvespec.SetupBunRouterWithResolveSpec(router, handler)
return router
}
// Or use the adapter
func setupBunRouterAdapter() *resolvespec.StandardBunRouterAdapter {
routerAdapter := resolvespec.NewStandardBunRouterAdapter()
// Register routes manually
routerAdapter.RegisterRouteWithParams("POST", "/:schema/:entity",
[]string{"schema", "entity"},
func(w http.ResponseWriter, r *http.Request, params map[string]string) {
// Your handler logic
})
return routerAdapter
}
// Full uptrace stack (bunrouter + Bun ORM)
func setupFullUptrace(bunDB *bun.DB) *bunrouter.Router {
// Database adapter
dbAdapter := resolvespec.NewBunAdapter(bunDB)
registry := resolvespec.NewModelRegistry()
handler := resolvespec.NewHandler(dbAdapter, registry)
// Router
router := resolvespec.NewStandardBunRouterAdapter()
resolvespec.SetupBunRouterWithResolveSpec(router.GetBunRouter(),
&resolvespec.APIHandlerCompat{
newHandler: handler,
})
return router.GetBunRouter()
}
Configuration
Model Registration
type User struct {
ID uint `json:"id" gorm:"primaryKey"`
Name string `json:"name"`
Email string `json:"email"`
Posts []Post `json:"posts,omitempty" gorm:"foreignKey:UserID"`
}
handler.RegisterModel("core", "users", &User{})
Features in Detail
Filtering
Supported operators:
- eq: Equal
- neq: Not Equal
- gt: Greater Than
- gte: Greater Than or Equal
- lt: Less Than
- lte: Less Than or Equal
- like: LIKE pattern matching
- ilike: Case-insensitive LIKE
- in: IN clause
Sorting
Support for multiple sort criteria with direction:
"sort": [
{
"column": "created_at",
"direction": "desc"
},
{
"column": "name",
"direction": "asc"
}
]
Computed Columns
Define virtual columns using SQL expressions:
"computedColumns": [
{
"name": "full_name",
"expression": "CONCAT(first_name, ' ', last_name)"
}
]
Testing
With New Architecture (Mockable)
import "github.com/stretchr/testify/mock"
// Create mock database
type MockDatabase struct {
mock.Mock
}
func (m *MockDatabase) NewSelect() resolvespec.SelectQuery {
args := m.Called()
return args.Get(0).(resolvespec.SelectQuery)
}
// Test your handler with mocks
func TestHandler(t *testing.T) {
mockDB := &MockDatabase{}
mockRegistry := resolvespec.NewModelRegistry()
handler := resolvespec.NewHandler(mockDB, mockRegistry)
// Setup mock expectations
mockDB.On("NewSelect").Return(&MockSelectQuery{})
// Test your logic
// ... test code
}
Security Considerations
- Implement proper authentication and authorization
- Validate all input parameters
- Use prepared statements (handled by GORM/Bun/your ORM)
- Implement rate limiting
- Control access at schema/entity level
- New: Database abstraction layer provides additional security through interface boundaries
Contributing
- Fork the repository
- Create your feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add some amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
License
This project is licensed under the MIT License - see the LICENSE file for details.
What's New
v2.1 (Latest)
RestHeadSpec - Header-Based REST API:
- Header-Based Querying: All query options via HTTP headers instead of request body
- Lifecycle Hooks: Before/after hooks for create, read, update, delete operations
- Cursor Pagination: Efficient cursor-based pagination with complex sorting
- Advanced Filtering: Field filters, search operators, AND/OR logic
- Multiple Response Formats: Simple, detailed, and Syncfusion-compatible responses
- Base64 Support: Base64-encoded header values for complex queries
- Type-Aware Filtering: Automatic type detection and conversion for filters
Core Improvements:
- Better model registry with schema.table format support
- Enhanced validation and error handling
- Improved reflection safety
- Fixed COUNT query issues with table aliasing
- Better pointer handling throughout the codebase
v2.0
Breaking Changes:
- None! Full backward compatibility maintained
New Features:
- Database Abstraction: Support for GORM, Bun, and custom ORMs
- Router Flexibility: Works with any HTTP router through adapters
- BunRouter Integration: Built-in support for uptrace/bunrouter
- Better Architecture: Clean separation of concerns with interfaces
- Enhanced Testing: Mockable interfaces for comprehensive testing
- Migration Guide: Step-by-step migration instructions
Performance Improvements:
- More efficient query building through interface design
- Reduced coupling between components
- Better memory management with interface boundaries
Acknowledgments
- Inspired by REST, OData, and GraphQL's flexibility
- Header-based approach: Inspired by REST best practices and clean API design
- Database Support: GORM and Bun
- Router Support: Gorilla Mux (built-in), BunRouter, Gin, Echo, and others through adapters
- Slogan generated using DALL-E
- AI used for documentation checking and correction
- Community feedback and contributions that made v2.0 and v2.1 possible
