Feature: Add GET /items/:id endpoint to retrieve a single item

[manish-jangra]

Description

The API currently supports GET /items (list all), POST /items (create), PATCH /items/:id (update), and DELETE /items/:id (delete) — but there is no way to retrieve a single item by its ID.

Adding GET /items/:id is a standard REST convention and would allow clients to fetch details of a specific todo item without downloading the entire list.

Use Case

• A client that only needs to display or verify one item shouldn't have to fetch all items and filter client-side.
• Follows RESTful resource design where every resource has its own URI.
• Useful for confirming an item's state after a PATCH operation or for deep-linking.

Proposed Implementation

@app.route("/items/<int:item_id>", methods=["GET"])
def get_item(item_id):
    items = _get_items()
    item = next((i for i in items if i["id"] == item_id), None)
    if item is None:
        return jsonify(error="item not found"), 404
    return jsonify(item)

Proposed Tests

def test_get_item(client):
    client.post("/items", json={"name": "My Task"})
    resp = client.get("/items/1")
    assert resp.status_code == 200
    data = resp.get_json()
    assert data["name"] == "My Task"
    assert data["id"] == 1

def test_get_item_not_found(client):
    resp = client.get("/items/999")
    assert resp.status_code == 404

Acceptance Criteria

• GET /items/:id returns the item as JSON with status 200
• Returns 404 with {"error": "item not found"} if the ID doesn't exist
• Unit tests cover both the happy path and not-found case
• README is updated with the new endpoint

[fullsend-ai-triage]

Triage Summary

Category: Feature request · Severity: Low

Problem

The API lacks a GET /items/:id endpoint for retrieving a single todo item by ID, which is a standard REST convention.

Recommended Implementation

Add a route handler for GET /items/<int:item_id> in app.py that:

• Looks up the item by ID in the items store
• Returns the item as JSON with status 200
• Returns {"error": "item not found"} with status 404 if the ID doesn't exist
• Update the README endpoint table accordingly

Proposed Test Case

def test_get_item_happy_path(client):
    # Create an item, then retrieve it by ID
    client.post("/items", json={"name": "My Task"})
    resp = client.get("/items/1")
    assert resp.status_code == 200
    data = resp.get_json()
    assert data["name"] == "My Task"
    assert data["id"] == 1

def test_get_item_not_found(client):
    # Request a non-existent item
    resp = client.get("/items/999")
    assert resp.status_code == 404
    assert resp.get_json()["error"] == "item not found"

Notes

• Issue Bug: ID collision after deleting items causes duplicate IDs #7 (ID collision bug) is related but does not block this work — the new endpoint can be implemented independently.
• The proposed implementation in the issue body aligns well with existing code patterns in app.py.
• To answer the follow-up question: yes, this issue has sufficient detail to proceed with implementation.

Previous run

Triage Summary

Category: Feature request · Severity: Low

Problem

The API lacks a GET /items/:id endpoint for retrieving a single todo item by ID, which is a standard REST convention.

Recommended Implementation

Add a route handler for GET /items/<int:item_id> in app.py that:

• Looks up the item by ID in the items store
• Returns the item as JSON with status 200
• Returns {"error": "item not found"} with status 404 if the ID doesn't exist
• Update the README endpoint table accordingly

Proposed Test Case

def test_get_item_happy_path(client):
    # Create an item, then retrieve it by ID
    client.post("/items", json={"name": "My Task"})
    resp = client.get("/items/1")
    assert resp.status_code == 200
    data = resp.get_json()
    assert data["name"] == "My Task"
    assert data["id"] == 1

def test_get_item_not_found(client):
    # Request a non-existent item
    resp = client.get("/items/999")
    assert resp.status_code == 404
    assert resp.get_json()["error"] == "item not found"

Notes

• Issue Bug: ID collision after deleting items causes duplicate IDs #7 (ID collision bug) is related but does not block this work — the new endpoint can be implemented independently.
• The proposed implementation in the issue body aligns well with existing code patterns in app.py.

---

Labels: This is a new feature request for an API enhancement, matching the 'enhancement' label.

[manish-jangra]

/fs-triage is this good enough to code or you need more info?

[manish-jangra]

/fs-triage I don't see "ready-to-code" label and how fs-code agent will be triggered

[manish-jangra]

/fs-code