You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A skipped change left its dependants unprotected: on the next cycle
they would be attempted and either fail spuriously (e.g.
`MISSING_PARENT`) or, worse, succeed partially and create an
orphan. The multi-error loop makes this more visible since
dependants are no longer shielded by the first-failure break.
When a change is skipped (automatically via `handleSyncError`
returning `'skipped'`, or by the user), the `syncBatch` loop now
adds it to `blockedIds`. Dependents detected via
`directPrerequisites` whose prereq has `doc.skipped === true` are
themselves skipped (`skipChange` persists the flag) and emit a
synthetic `SKIPPED_DEPENDENCY` alert. `blockedIds` propagates
the skip transitively across the topologically ordered batch.
The synthetic `SyncError` carries `prereqPath` as a dedicated
field, transported by `makeAlert` to the GUI. `viewByCode`
interpolates it into a localized message with the path wrapped
in backticks. The restored `Util.DecorationParser` parses those
backticks in `alertContent`, and `decoratedName` renders the path
as a clickable chip (blue background, `title` with full path,
`ShowInParent` on click).
0 commit comments