Skip to content

Wrap every function in Invoke in the expose-a-use-case skill - #53

Merged
stphnwlsh merged 1 commit into
mainfrom
fix/expose-use-case-invoke
Nov 8, 2026
Merged

stphnwlsh merged 1 commit into
mainfrom
fix/expose-use-case-invoke

Conversation

@stphnwlsh

@stphnwlsh stphnwlsh commented Nov 8, 2026 •

Copy link
Copy Markdown
Member

Summary

The skill told agents to call Send on its own, so a function written from it compiled and worked but left no trace span, and its metrics waited for the next invocation to be flushed. The description, step 4 and the example now wrap the body in this.Invoke(request, context, ...), as every function in the template does, and the Don't list says what goes wrong without it. Found while checking the Add a function guide on the docs site against a fresh solution.

Related issues

Follows LeanMeanCleanApps/.github#78.

Type of change

  • Bug fix
  • New feature
  • Breaking change (the generated solution or template parameters change in a way existing users will notice)
  • Refactoring or clean-up
  • Documentation
  • Build, pipeline or dependency update

Shared layers

  • This only touches the Presentation layer of this template.
  • This touches the Application or Infrastructure layers, tests, pipeline or repository setup, so it needs to be carried across all five templates.

Checklist

  • dotnet build and dotnet test pass locally with no warnings. (No code changed; the skill's example matches LambdaFunction.cs as it is.)
  • I added or updated tests, and line coverage stays at or above 95%. (Not needed, docs only.)
  • I updated the README or docs where behaviour changed. (The Add a function guide on the site already shows Invoke.)
  • If this changes how we do something, I updated the matching skill in .agents/skills.
  • I checked the template still installs and creates a working solution (see CONTRIBUTING.md). (The skill ships in the package unchanged in shape; nothing else moved.)

The skill told agents to call Send on its own, so a function written from
it left no trace span and its metrics waited for the next invocation to be
sent. The example and the steps now wrap the body in Invoke, as every
function in the template does, and the Don't list says why.
@github-actions github-actions Bot added the bug Something isn't working label Nov 8, 2026
@stphnwlsh stphnwlsh self-assigned this Nov 8, 2026
@github-actions

github-actions Bot commented Nov 8, 2026

Copy link
Copy Markdown

Build Pipeline

✅ Ready to merge. Every stage passed.

Stage Result Details
Build 🟢 Passed Version 2026.11.08.183-pr-53 · Template package 211 KB
Test 🟢 Passed 203 passed · 0 failed · 0 skipped · Template installs, builds and passes its tests
Coverage 🟢 Passed 100% (792 of 792 lines) · Needs 95%
Static Analysis 🟢 Passed No open CodeQL alerts
Dependency Review 🟢 Passed 0 vulnerable packages · 0 licence problems
Container Scan 🟢 Passed Image starts and answers · 3 open Trivy alerts, none blocking: 1 medium, 1 low, 1 note · 1 ignored in .trivyignore

Commit ca4213f · Full run

@stphnwlsh
stphnwlsh merged commit 4490cd1 into main Nov 8, 2026
13 checks passed
@stphnwlsh
stphnwlsh deleted the fix/expose-use-case-invoke branch November 8, 2026 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant