IDE Publish action (#189) + Republish-all / republish result UI (#181) — 2.2.0#42
Merged
Merged
Conversation
The IDE could only Save; add a Publish action for publishable file types (pages + scripts → S3): - Green rocket button in the tab bar, shown only for page/script tabs. - Ctrl+Shift+S shortcut (Save stays Ctrl+S); added to the welcome shortcuts. - Publish sends state=1 with the content, so the backend runs its normal publish path (publishPage / handleScriptPublication → S3) and versions it. Allowed even when not dirty (re-deploy); persists pending edits in the same request. Bump KS_VERSION + package.json to 2.2.0. esbuild build passes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
On the app configuration page: a "Republish all pages" button on the Auth Mode card (re-stamps every published page with the current connect code), and surface the per-page republish_summary (succeeded/failed + failures) returned by kyte-php v4.8.1 in the auth-mode/kyte-connect flows and the new button — instead of a blind success toast. Folded into the IDE-Publish branch (2.2.0). esbuild build passes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Same-named files (common for pages) were indistinguishable in the explorer without opening each. Render the path in a muted second line under the file name (pages & scripts only), with the full path as a hover tooltip. - renderGroup: wrap name+path in a flex-column .file-meta; path shown when set. - renderPagesSection/renderScriptsSection: attach path = s3key. - kyte-ide.css: .file-meta / .file-path styles. esbuild build passes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
IDE Publish action (#189) + "Republish all pages" / republish result UI (#181) — 2.2.0
Two related Shipyard UX additions, paired with kyte-php v4.8.1 (PR keyqcloud/kyte-php#97).
#189 — Publish action in the IDE
The in-app IDE could only Save; there was no way to Publish (deploy to S3) from it.
state=1with the content → backend runs its normal publish path (page →publishPage→ S3 + CloudFront; script →handleScriptPublication→ S3) and versions it. Allowed even when not dirty (re-deploy); persists pending edits in the same request.#181 — "Republish all pages" + per-page result
Pairs with kyte-php v4.8.1's fault-isolated republish (which returns a
republish_summary).republish_summaryand report how many pages succeeded/failed (failures listed + logged), instead of a blind "it worked" toast.Bumps to 2.2.0 (
KS_VERSION+package.json). esbuild build passes.Note: the "IDE save didn't persist" bug from #189 was already fixed by kyte-php v4.8.0's guard relaxation — confirmed working on dev.
🤖 Generated with Claude Code