feat(admin): normalize roadmap and publish safety#11
Merged
Conversation
coding-hui
changed the title
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6624d2fc6e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
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
1 participant
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.
Summary
.techexecution plan.Why
The admin UI exposes pre-publish checks and allows selecting Published while creating a ready paper. Backend APIs still need to reject direct invalid publish attempts, so the UI save flow now matches the service contract: content is persisted first, then status is promoted after validation.
Validation
go test ./internal/library -run 'PublishPaper' -vgo test ./...pnpm --dir apps/admin jest --runInBandpnpm --dir apps/admin lintpnpm --dir apps/admin buildhttp://localhost:8004against API8083: empty paper publish rejected, draft-paper exam publish rejected, valid paper/exam publish succeeds.POST status=PUBLISHEDrejected, browser-origin save sequencePOST Draft -> PUT outline -> PUT Publishedsucceeds with final paper statusPUBLISHED, 1 question, total score 10.