Repository navigation
chore: fetch a single task from the v1 API path - #591
Merged
anoopcodehack merged 1 commit intoOct 9, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #562
Most of #562 was already fixed: the client moved to /api/v1, and the server keeps /api/tasks as an alias, so nothing returns 404 anymore. One call was still on the old path:
viewTaskin BoardContext.jsx fetched a single task from/api/tasks/:id. This moves it to/api/v1/tasks/:idlike everything else, so no client code depends on the alias anymore.Tested locally against a real MongoDB: both paths return 200 for an existing task, and the client builds.