`goat` polish
Opened this issue · 3 comments
bnewbold commented
packaging:
- homebrew cask (?)
- debian/ubuntu packages
- command to check for updates
- maybe move to a separate repo
- tests, any tests
features:
- "debug" helpers: custom domain handles, self-hosted ozone, self-hosted PDS
- lexicon validation
- generic XRPC endpoint calls
- PLC validation and create/submit ops
- account migration
- ozone: reporting, history, event stream?
- dump label stream
- PDS admin: takedown, create accounts, invites
bsky features:
- parsing text facets
- post embeds: images, records, URLs
- bsky.app URL / AT-URI helper (including
goat bsky get
?) - timeline, feeds, rendering
- search
- some things only work with record types known to indigo; should be generic
interface polish:
-
--json
output for commands which aren't - color: errors, JSON pretty-print
- allow
-
for stdin - switch to something other than
urfave/cli
so CLI args are handled reasonably
tom-sherman commented
Any chance of being able to accept inputs via stdin and/or positional argument as well as the file for record create
?
bnewbold commented
@tom-sherman yes! I'd probably do it by special-casing -
as the file path, and have folks do ./-
if they really want a file named -
.
echo "{whatever}" | jq . | goat record create -
Would that work for you?
tom-sherman commented
Would that work for you?
Yes!