Add JSON APIs for projects, plans, and builds - #144
Closed
tkadauke-syrus[bot] wants to merge 2 commits into
Closed
tkadauke-syrus[bot] wants to merge 2 commits into
tkadauke-syrus[bot] wants to merge 2 commits into
Conversation
tkadauke-syrus
Bot
force-pushed
the
syrus/direct-866
branch
2 times, most recently
from
June 11, 2026 13:31
89b8c69 to
e485050
Compare
Expose project and plan management data for the React migration through JSON endpoints, including plan stats, relationships, detail payloads, and manual build creation responses suitable for client navigation. Implemented API controllers, scoped routes, permission-aware parameter handling for plan steps, validation/error JSON responses, and nested build route support. Added functional coverage for CRUD permissions, plan serialization, child chain behavior, admin-only steps, and manual build triggering. Co-Authored-By: Thomas Kadauke <thomas.kadauke@googlemail.com>
tkadauke-syrus
Bot
force-pushed
the
syrus/direct-866
branch
from
June 11, 2026 14:00
e485050 to
bf6183d
Compare
CI was failing because Vite resolved extensionless imports to legacy `.js` modules before the newer TypeScript sources, which caused missing export errors during the test asset build. The Vite resolver now prefers `.tsx` and `.ts` before `.js` so the React entrypoint builds correctly. The API build lookup test also expected `ActiveRecord::RecordNotFound` to escape the controller, but API controllers render that as JSON 404. The test now asserts the intended not-found API response while preserving the database-id lookup coverage. Co-Authored-By: Thomas Kadauke <thomas.kadauke@googlemail.com>
Contributor
Author
|
Landed via Epic merge-train (integration PR #170). Job #866. |
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
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.
Expose project and plan management data for the React migration through JSON endpoints, including plan stats, relationships, detail payloads, and manual build creation responses suitable for client navigation.
Implemented API controllers, scoped routes, permission-aware parameter handling for plan steps, validation/error JSON responses, and nested build route support. Added functional coverage for CRUD permissions, plan serialization, child chain behavior, admin-only steps, and manual build triggering.
Triggered by @tkadauke
Authored by Codex (trigger=initial). Review carefully.
This PR was implemented by Syrus across 19 Runs at a total cost of $0.00.