v1.35.1

Release v1.35.1

🛠 Improvements

1. Kafka Connection & Security Enhancements

• Added support for configuring Kafka with extra connection and security parameters to seamlessly integrate with Confluent Kafka SaaS and similar platforms.

• Introduced three new configuration options for SASL authentication:

  🔧 KAFKA_SASL_MECHANISM

  • SASL mechanism for authentication (e.g. PLAIN, SCRAM-SHA-256, SCRAM-SHA-512)
  • Default: None

  🔧 KAFKA_SASL_USERNAME

  • Username for SASL authentication
  • Default: None

  🔧 KAFKA_SASL_PASSWORD

  • Password for SASL authentication
  • Default: None

2. Multiple Static Folders Support

• Multiple static folders can now be registered and served at different custom endpoints.

• Example usage:

    package main 
    
    import  "gofr.dev/pkg/gofr"  

	func  main() {
        app := gofr.New()
        app.AddStaticFiles("public", "./public")
        app.AddStaticFiles("static", "./static")
        app.Run()
    }

• In this example:

  • Files in the public folder are served at host/public/*
  • Files in the static folder are served at host/static/*

3. ArangoDB Resource Creation Enhanced

• CreateDB, CreateGraph, and CreateCollection methods in Arango, now check for existing resources before creating them. Check out our official documentation to know more.

🛠 Fixes

1. Fixed Static File Server Endpoint Handling

• Previously, files in the static directory were served by default at /static/. If the same directory was registered at another path, the files were being served at both endpoints, resulting in duplicate serving.
• This has now been fixed. If a user registers a custom endpoint using app.AddStaticFiles({custom-endpoint}, ./static), GoFr will automatically serve the files only at the specified custom endpoint.
• Additionally, if any directories are re-registered within the GoFr application, the files will now be served at the latest registered endpoint, ensuring there’s no duplication.