Conversation
…n't get lost when regenerated
| routes = [{ method: 'GET', path: '/health', description: 'Health check' }]; | ||
| } | ||
|
|
||
| const description = options.description || `TODO: Add a description of the ${handlerName} lambda.`; |
There was a problem hiding this comment.
When a new lambda is generated, it will be on the developer of that PR to update the description (if it's regenerating for an old lambda the description won't change). Is this fine or do we want to use another template description to reduce the number of potentially forgotten todo's (like "Lambda for ${handlerName}")
There was a problem hiding this comment.
Good question, I think its ok to leave the TODO, hopefully either the dev or one of the reviewers will catch it.
denniwang
left a comment
denniwang
left a comment
There was a problem hiding this comment.
LGTM, looks like we need to write a lot more documentation though...
| routes = [{ method: 'GET', path: '/health', description: 'Health check' }]; | ||
| } | ||
|
|
||
| const description = options.description || `TODO: Add a description of the ${handlerName} lambda.`; |
There was a problem hiding this comment.
Good question, I think its ok to leave the TODO, hopefully either the dev or one of the reviewers will catch it.
2 participants
ℹ️ Issue
Closes #94
📝 Description
Write a short summary of what you added. Why is it important? Any member of C4C should be able to read this and understand your contribution -- not just your team members.
generate-readmecommand to the lambda CLI tool with a general template displaying setup, endpoint, and test information✔️ Verification
What steps did you take to verify your changes work? These should be clear enough for someone to be able to clone the branch and follow the steps themselves.
Tested by using CLI to make a
test-lambda, which generated this READMEYou can also see it in action in this PR! After I updated this branch from main, the GitHub actions bot generated a readme for the new
authlambda.🏕️ (Optional) Future Work / Notes
Did you notice anything ugly during the course of this ticket? Any bugs, design challenges, or unexpected behavior? Write it down so we can clean it up in a future ticket!