startautomating / psa Goto Github PK

• #25
• #26
• #27
• #28
• #29
• #35
• #37
• #38
• #39
• #40
• #43
• #44

Common parameters can have common documentation.

• #18
• #19
• #6
• #7
• #8
• #9
• #20

Each .defs file within the at protocol contains information multiple endpoints are likely to reference.

To make a more perfect wrapper of At Protocol, we want to make .defs files into commands that describe the definitions contained within.

For useful bonus points, we want a type reference to "just work"

• #22
• #23
• #24

• #30
• #32
• #33

PSA is a PowerShell Module for Announcements (using the At Protocol, or any protocol we'd like)

It is built by:

• #2
  • #3
  • #4
  • #5
• #17
  • #18
  • #19
  • #6
  • #7
  • #8
• #9
  • #10
  • #11
  • #12
  • #13
  • #14
• #16
• #15

We will want to accumulate piped input and run in the end block.

We will also want to special-case a body parameter with a binding of ".". This should be sent as a request body.

Display in color, use the .MarkdownDescription (#32 ) where possible, and link to profile/followers/follows.

Any at protocol command that returns a strongly defined property should propagate that decoration into the output objects.

This should happen recursively.

This way, any known objects in any return from anything in at can be formatted and extended.

Ensure that the atProto directory is excluded from publish

• #21

• #34

  • #22
  • #23
  • #24

• #31

  • #30
  • #32
  • #33
  • #45
  • #46
  • #47
  • #48
  • #49

• #50
• #51
• #52
• #53
• #54

To do this, we'll need to be sure that:

• #41

Additionally, it should remove the property "Password" by default.

The lexicon is ordered into subdirectories. Whenever possible, we should do the same.

Additionally, commands should derive their nouns from the second word in the lexicon (the domain).