Skip to content

Clarify JSON body structure for PATCH requests#188

Merged
royemosby merged 1 commit into
mainfrom
royemosby-patch-1
May 19, 2026
Merged

Clarify JSON body structure for PATCH requests#188
royemosby merged 1 commit into
mainfrom
royemosby-patch-1

Conversation

@royemosby
Copy link
Copy Markdown
Collaborator

Updated the JSON body requirements for PATCH requests in the assignment instructions.

Brief Summary of Proposed Changes

Rationale for Proposed Changes

Link to any Related Issues

Confirm

  • All text follows the GitHub Flavored Markdown Spec and is organized using the correct heading levels.
  • All new pictures or media include descriptive alt text.
  • Code blocks have been formatted and given the appropriate language label.

Updated the JSON body requirements for PATCH requests in the assignment instructions.
Copilot AI review requested due to automatic review settings May 19, 2026 22:37
@royemosby royemosby merged commit f6ad391 into main May 19, 2026
@royemosby royemosby deleted the royemosby-patch-1 branch May 19, 2026 22:38
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Lesson 07 assignment instructions to clarify what students should include in the JSON request body when making PATCH requests to the /api/tasks/:id endpoint.

Changes:

  • Removed createdAt from the required JSON body for the completeTodo PATCH request.
  • Updated the updateTodo PATCH body description to specify which fields should be sent.
  • Fixed blockquote indentation so the final AirHub [!NOTE] callout renders correctly.

- **Optimistically apply** the edited todo to state
- Make a PATCH request to `/api/tasks/${editedTodo.id}` with:
- JSON body containing title, isCompleted, and createdAt
- JSON body containing `title` and `isCompleted` with associated values

> [!NOTE]
> The AI review tool (known as AirHub) can check code and structure, but it does not run your code in a server environment to verify that aspect runs properly. We will have human reviewers checking this aspect, so you may receive a passing assignment from AirHub that could still need revisions after a human has checked that your work runs properly in the correct environment. If your AI and human reviewer feedbacks don't match, trust the human review. No newline at end of file
> The AI review tool (known as AirHub) can check code and structure, but it does not run your code in a server environment to verify that aspect runs properly. We will have human reviewers checking this aspect, so you may receive a passing assignment from AirHub that could still need revisions after a human has checked that your work runs properly in the correct environment. If your AI and human reviewer feedbacks don't match, trust the human review.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants