Backend: Add routes-f update endpoint

[davedumto]

Summary

Add an update endpoint for Routes-F items with optimistic concurrency.

Requirements

• PATCH /api/routes-f/items/[id] accepts partial updates.
• Require If-Match header for concurrency control.
• Return 412 if ETag mismatch.

Notes

• Mock item store acceptable.

Acceptance Criteria

• Missing If-Match returns 428.
• ETag mismatch returns 412.
• Tests cover concurrency flow.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[David-patrick-chuks]

@David-patrick-chuks has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Kindly assign this to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @David-patrick-chuks to this issue.

[Jay-Peter-Egemasi]

@Jay-Peter-Egemasi has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi, I’m Jerome, a backend developer experienced in building RESTful APIs with proper validation and concurrency control.

I’d like to take on issue #299 (Add routes-f update endpoint).

I will implement the PATCH /api/routes-f/items/[id] endpoint supporting partial updates with optimistic concurrency using the If-Match header. The endpoint will return 428 when If-Match is missing and 412 when the ETag does not match, ensuring safe update flows. A mock in-memory store will be used and structured to be easily replaceable with a real database later.

I’ll also include tests covering the full concurrency flow and error cases.

Estimated completion time: within 24–48 hours.

Happy to get started right away.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Jay-Peter-Egemasi to this issue.

[drips-wave]

Congratulations, @Jay-Peter-Egemasi! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @Jay-Peter-Egemasi: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are issued when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @Jay-Peter-Egemasi as part of the Stellar Wave Program's 2nd Wave 🥳

😎 @Jay-Peter-Egemasi: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.