📄️ Configuration File
The Gleece configuration file, usually named gleece.config.json, contains all the mandatory and available configurations and options to customize the code and specification generator.
📄️ Command Line interface
Gleece is designed to run in CI/CD flows and during builds.
📄️ Routing
Gleece is designed to minimize HTTP routing boilerplate code, allowing developers to focus on business logic.
📄️ Modeling
Gleece controllers allow you to use standard Go primitives, structs, and type aliases as function parameters and return types. During the build process, Gleece analyzes all structs and type aliases used across API controllers to generate the routes and model specifications.
📄️ Specification
One of Gleece's powerful features is its automatic OpenAPI specification generation directly from your codebase.
📄️ Authorization
Gleece handles security on both sides: the declaration of required security and scope, which is defined by the Security annotation, and the processing of the check itself through a supplied check function that will be called once a request arrives.
📄️ Error Handling
Each route function must declare a return type of error. If there is no response payload, error will be the only return type. If there is a payload response, error will be the second and last return type.
📄️ Data Validation
Input validation in Gleece is simplified through the use of go-playground/validator v10 format.