refactor: rename framework from AwsLambda.Host to MinimalLambda#227
Merged
Conversation
- Updated project namespaces and references from AwsLambda.Host to MinimalLambda. - Changed all package names and documentation references to align with MinimalLambda branding. - Adjusted example projects and unit tests to reflect the renaming.
- Replaced all occurrences of the `MinimalLambda.Host` namespace with `MinimalLambda`. - Updated related unit tests, examples, and benchmark projects to use the new namespace. - Adjusted global using directives and documentation references accordingly.
- Included required namespaces in example and benchmark projects. - Ensured consistency with the updated project structure.
… from TypeInfo usages - Simplified `Microsoft.CodeAnalysis.TypeInfo` to `TypeInfo` across HandlerInfoExtractor.cs. - Maintained consistency with project-wide namespace simplifications.
…sions - Added `Microsoft.Extensions.DependencyInjection` imports in `RequestEnvelopeMiddleware.cs` and `OutputFormattingLambdaApplicationExtensions.cs`. - Included `MinimalLambda.Envelopes` import in `RequestEnvelopeMiddleware.cs`.
- Replaced unqualified `Options.Create` with `Microsoft.Extensions.Options.Options.Create` in tests. - Included missing namespace imports in relevant test files for consistency.
…ency - Renamed `AwsLambda.Host.targets` to `MinimalLambda.Core.targets` for clarity. - Updated project file references to reflect the new build target file name. - Adjusted `InitialTargets` and `Target` name to align with the new naming convention. - Removed obsolete folder and restructured build file inclusion. - Ensured consistent packaging metadata in project file.
- Updated solution file name to align with the MinimalLambda branding.
…aHost
Simplify the configuration section name from "AwsLambdaHost" to "LambdaHost"
for better clarity and conciseness. This change affects how users configure
the Lambda host in appsettings.json and environment variables.
BREAKING CHANGE: Configuration section name changed from "AwsLambdaHost" to "LambdaHost"
Users must update their configuration files:
Before:
{
"AwsLambdaHost": {
"InvocationCancellationBuffer": "00:00:05"
}
}
After:
{
"LambdaHost": {
"InvocationCancellationBuffer": "00:00:05"
}
}
Environment variables must also be updated:
- AwsLambdaHost__InvocationCancellationBuffer → LambdaHost__InvocationCancellationBuffer
- Pattern: AwsLambdaHost__* → LambdaHost__*
Update remaining "AWS Lambda Host" references to "MinimalLambda" in CONTRIBUTING.md and package.json description.
… global usings - Removed unused `build/MinimalLambda.targets` and associated references from the project file. - Deleted redundant global `MinimalLambda` using directives in `GlobalUsings.cs`.
- Introduced `GenericHandler.scriban` for generating generic handler extensions. - Added `MapHandler.scriban` to support mapping of lambda handlers with event/response features. - Created `InterceptsLocationAttribute.scriban` for method-level interception metadata generation. - Updated `.gitignore` to properly exclude temporary and environment-specific files. - Modified `HandlerInfoExtractor.cs` to adapt to the `MinimalLambda` namespace changes.
…Scriban templates - Cleaned up unnecessary trailing whitespace in `GenericHandler.scriban`. - Removed trailing whitespace in `InterceptsLocationAttribute.scriban`. - Fixed whitespace issues in `MapHandler.scriban` for improved readability.
…LocationAttribute.scriban - Cleaned up unnecessary trailing whitespace for improved template readability.
- Deleted outdated `LambdaHandler.g.verified.cs` snapshots for test cases: - `ExpressionLambdaVerifyTests` - `OnInitVerifyTests` - `OnShutdownVerifyTests` - Cleaned up unnecessary snapshot files no longer in use.
Update all major documentation to highlight the ASP.NET Core Minimal API coding pattern while clarifying this works for ANY Lambda trigger type: - Lead with 'If you know ASP.NET Core Minimal APIs, you already know MinimalLambda' - Add comparison table showing ASP.NET Core → MinimalLambda equivalents - Reorder key features to lead with Minimal API Pattern - Clarify 'for any trigger' (SQS, SNS, Kinesis, S3, EventBridge, API Gateway, etc.) - Update package descriptions to be concise: 'Minimal API-style framework for AWS Lambda functions' - Emphasize this is about the coding PATTERN, not just HTTP/API events This makes it clear that MinimalLambda uses familiar ASP.NET Core coding patterns but works across all Lambda event sources.
…operties - Updated `InterceptorsNamespaces` to include `MinimalLambda.Generated` instead of `MinimalLambda`. - Removed unused `RootNamespace` property from `MinimalLambda.csproj`. - Cleaned up unnecessary empty `<ItemGroup>` in `MinimalLambda.Example.HelloWorld.csproj`.
Update all package Description tags to be concise and follow industry patterns: - MinimalLambda: 'Minimal API-style framework for AWS Lambda functions' - MinimalLambda.Abstractions: 'Core abstractions for MinimalLambda' - MinimalLambda.OpenTelemetry: 'OpenTelemetry integration for MinimalLambda' - All envelope packages: 'Strongly-typed [EventSource] event envelopes' This provides clear, consistent metadata for NuGet package listings.
j-d-ha
changed the title
Updated across multiple files to align with the updated naming convention: - Adjusted `RootNamespace` in project files to use `MinimalLambda`. - Updated `AWS_LAMBDA_FUNCTION_NAME` values in launch settings for consistency. - Changed documentation references in `CLAUDE.md` and `CONTRIBUTING.md` to reflect the new naming. This ensures consistency throughout the project following namespace changes.
- Removed redundant global `MinimalLambda` and `MinimalLambda.Options` usings. - Simplified `GlobalUsings.cs` for improved clarity and maintainability.
…ng Scriban templates - Introduced `TemplateHelper` class to load templates from embedded resources. - Added error handling for missing or invalid template resources. - Updated `.gitignore` to refine exclusion of temporary `.cs` files.
j-d-ha
enabled auto-merge (squash)
December 11, 2025 19:07
j-d-ha
disabled auto-merge
December 11, 2025 19:14
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚀 Pull Request
📋 Summary
This PR completes a comprehensive renaming of the entire framework from
AwsLambda.HosttoMinimalLambda. This rebrand better reflects the framework's philosophy of bringing ASP.NET Core Minimal API patterns to AWS Lambda development for any trigger type.Key Changes:
AwsLambda.Host.*toMinimalLambda.*AwsLambda.Host→MinimalLambdaAwsLambda.Host.Abstractions→MinimalLambda.AbstractionsAwsLambda.Host.OpenTelemetry→MinimalLambda.OpenTelemetryAwsLambda.Host.slntoMinimalLambda.sln2.0.0-beta.1to reflect breaking changesaws-lambda-hosttominimal-lambda✅ Checklist
🧪 Related Issues or PRs
This addresses the framework's positioning and makes the naming more intuitive for developers familiar with ASP.NET Core Minimal APIs.
💬 Notes for Reviewers
This is a major breaking change that affects all users of the framework. Key review areas:
BREAKING CHANGE
The entire framework has been renamed from
AwsLambda.HosttoMinimalLambda. All package names, namespaces, and public APIs now use theMinimalLambdaprefix instead ofAwsLambda.Host.Migration Required:
AwsLambda.Host*toMinimalLambda*usingstatements fromAwsLambda.HosttoMinimalLambdaAwsLambdaHosttoLambdaHostThis is a major version bump (2.0.0) to reflect the breaking nature of this change.