Repository navigation
docs(docs): show the automation editor, run and trigger screens - #4701
Merged
Merged
Conversation
The skip notice reads "It came due on {at}", and a start skipped today
gave {at} as a bare time: "It came due on 11:00 AM". The notice now always
gives a day and a time, as the trigger's last-run line does.
A run that failed in code said "The code threw a Error." The failure sentences now say "an error" for a plain Error, "an EvalError" for that name, and keep "a TypeError" for the rest; German and French say "einen Fehler" and "une erreur" for a plain Error.
…e picker The runs table opens a run from its row now, not from a link, so the docs capture and the canvas e2e spec click the row that carries the run's status. The schedule picker's presets are a radio group and its next runs are named with their zone; the tall trigger shots get a window that holds the whole section, or the part below the fold is captured blank. The demo seed reads the embedding switch only after the page unmasks, accepts the 201 a first save answers, clicks Test run until the start request leaves, and asks the runs API whether a run exists instead of waiting out a row that never renders.
Fourteen screenshots for what the editor, the run page and the trigger settings now do: Start's fields, the possible paths, a node's shape, code completion, the source, the problems list and the phone layout; a failed run; the schedule presets, custom times and interval, a webhook, the event list and a skipped start. English, German and French captions and alt text; the captures are shared.
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.
Fourteen docs screenshots for the editor, run page and trigger work that landed without images. Capturing them surfaced two product wording bugs and stale capture selectors.
Docs (en/de/fr)
editor.md: phone layout, possible paths, a node's Shape tab, code completion, Start's fields, the Source view, the Problems list.execution-logs.md#failures: a failed run.triggers.md: schedule presets, custom times, custom interval, a webhook in two projects, the event list, and a skipped start under "Diagnose a missing start".Product fixes found in the shots
Capture and e2e
automation-canvas.spec.tsnow click the row with the run's status.Checks run locally
lint:links: every link lands.tsc: clean.oxlint --type-awareon touched files: 0 issues.automation-canvas.spec.tsagainst a local stack: passed.Known gap, not in this PR: the seed's project-agents step finds no model in the New agent dialog on a fresh capture stack. The automation shots were captured around it with
--skip-seed.