typespec-api-operations

Add RESTful operations to an existing TypeSpec API plugin for Microsoft 365 Copilot. Create the Adaptive Card ( appPackage/item-card.json ): After adding operations, test with these prompts: GET Operations: POST Operations: PATCH Operations: DELETE Operations: Solution : Check parameter is properly decorated with @query , @path , or @body Solution : Verify file path in @card decorator and check JSON syntax Solution : Ensure @capabilities decorator is properly formatted with confirmation object Solution : Check if property needs @visibility(Lifecycle.Read) or remove it if it should be writable - "List all items and show them in a table" - "Show me items for user ID 1" - "Get the details of item 42" - "Create a new item with title 'My Task' for user 1" - "Add an item: title 'New Feature', description 'Add login'" - "Update item 10 with title 'Updated Title'" - "Change the status of item 5 to completed" - "Delete item 99" - "Remove the item with ID 15" - Use descriptive parameter names: userId not uid - Be consistent across operations - Use optional parameters ( ? ) for filters - Add JSDoc comments to all operations - Describe what each parameter does - Document expected responses - Use @visibility(Lifecycle.Read) for read-only fields like id - Use @format("date-time") for date fields - Use union types for enums: "active" | "completed" - Make optional fields explicit with ? -...