5
0
mirror of https://github.com/wailsapp/wails.git synced 2025-05-03 23:21:58 +08:00
wails/v3/examples/gin-example
Lea Anthony b72782c35d
Update docs + examples.
Serve runtime from assetserver if requested.
2025-03-11 08:50:03 +11:00
..
static Update docs + examples. 2025-03-11 08:50:03 +11:00
go.mod Add gin guide, fix asset server merge, add gin example 2025-03-09 15:58:50 +11:00
go.sum Add gin guide, fix asset server merge, add gin example 2025-03-09 15:58:50 +11:00
main.go Update docs + examples. 2025-03-11 08:50:03 +11:00
README.md Add gin example 2025-03-09 14:38:46 +11:00

Gin Example

This example demonstrates how to use the Gin web framework with Wails.

Overview

This example shows how to:

  • Set up Gin as the asset handler for a Wails application
  • Create a middleware that routes requests between Wails and Gin
  • Define API endpoints with Gin
  • Communicate between the Gin-served frontend and Wails backend
  • Implement custom Gin middleware

Running the Example

cd v3/examples/gin-example
go mod tidy
go run .

How It Works

The example uses Gin's HTTP router to serve the frontend content whilst still allowing Wails to handle its internal routes. This is achieved through:

  1. Creating a Gin router with routes for the frontend
  2. Implementing a middleware function that decides whether to pass requests to Gin or let Wails handle them
  3. Configuring the Wails application to use both the Gin router as the asset handler and the custom middleware

Wails-Gin Integration

The key part of the integration is the middleware function:

func GinMiddleware(ginEngine *gin.Engine) application.Middleware {
    return func(next http.Handler) http.Handler {
        return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
            // Let Wails handle its internal routes
            if r.URL.Path == "/wails/runtime.js" || r.URL.Path == "/wails/ipc" {
                next.ServeHTTP(w, r)
                return
            }

            // Let Gin handle everything else
            ginEngine.ServeHTTP(w, r)
        })
    }
}

This allows you to leverage Gin's powerful routing and middleware capabilities whilst still maintaining full access to Wails features.

Custom Gin Middleware

The example also demonstrates how to create custom Gin middleware:

func LoggingMiddleware() gin.HandlerFunc {
    return func(c *gin.Context) {
        // Start timer
        startTime := time.Now()

        // Process request
        c.Next()

        // Calculate latency
        latency := time.Since(startTime)

        // Log request details
        log.Printf("[GIN] %s | %s | %s | %d | %s",
            c.Request.Method,
            c.Request.URL.Path,
            c.ClientIP(),
            c.Writer.Status(),
            latency,
        )
    }
}

This middleware is applied to all Gin routes and logs details about each request.

Application Configuration

The Wails application is configured to use Gin as follows:

app := application.New(application.Options{
    Name:        "Gin Example",
    Description: "A demo of using Gin with Wails",
    Mac: application.MacOptions{
        ApplicationShouldTerminateAfterLastWindowClosed: true,
    },
    Assets: application.AssetOptions{
        Handler:    ginEngine,
        Middleware: GinMiddleware(ginEngine),
    },
})

This configuration tells Wails to:

  1. Use the Gin engine as the primary handler for HTTP requests
  2. Use our custom middleware to route requests between Wails and Gin