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
-I is the format whose contract is "identifier only" — it is what pipelines read. Every
other result type honours it. Getting prose here breaks the composition this project is
built around:
-I should emit the affected identifier (the deleted post's at://… URI, which SuccessResult already carries in data["deleted"])
Decide -T and -L: -T as the message is defensible; -L should probably show the
operation and its target
Consider whether SuccessResult should carry a declared identifier field rather than
each command inventing a data key, since more mutating commands are coming (feat: Add like / unlike commands #87)
Acceptance criteria
ssky delete <uri> -I prints the URI and nothing else
Behavior specified in docs/OUTPUT_FORMATS.md and the divergence row removed
Part of #72. Found while writing
docs/OUTPUT_FORMATS.md(#76).Problem
SuccessResult.print()only branches on JSON vs non-JSON:So
id,text, andlongall collapse to the human message.deleteis the onlycommand returning this type, which means:
-Iis the format whose contract is "identifier only" — it is what pipelines read. Everyother result type honours it. Getting prose here breaks the composition this project is
built around:
Work
-Ishould emit the affected identifier (the deleted post'sat://…URI, whichSuccessResultalready carries indata["deleted"])-Tand-L:-Tas the message is defensible;-Lshould probably show theoperation and its target
SuccessResultshould carry a declared identifier field rather thaneach command inventing a
datakey, since more mutating commands are coming (feat: Add like / unlike commands #87)Acceptance criteria
ssky delete <uri> -Iprints the URI and nothing elsedocs/OUTPUT_FORMATS.mdand the divergence row removed-Ion a mutating command