Optargs

[RobSanders]

Initial 'functionally complete' status. Passes Covertity scan with '--aggressiveness medium --concurrenty --security --enable-fnptr --enable-callgraph-metrics' as scanning flags Passes valgrind checks with '--leak-check=full --show-leak-kinds=all' as flags

• clitest has command 'perimeter' showing optarg with arguments, optional flags, optional arguments, the 'multiple' flag, and build mode
• filters section re-written so all legacy filters now using the optarg parsing code
• added new CLI_CMD_HYPHENATED_OPTION to allow for '-ive' parsing for grep/egrep filters.
• validator for this works, could update completor to enable constructing of individual flags
• undemonstrated (yet) but working in our code that link w/libcli is the cli_comphelp object has a field 'comma_separated' which can be set by a completor to indicate that the field is a comma separated list of entries, so a 'chosen' field will be appended starting at the last comma or beginning-of-field as appropriate. A similar sort of thing could be done for compositing a argument such as the '-ive' flag for the grep/egrep filters.

[ghost]

There were the following issues with this Pull Request

• Commit: 6a3ab54c390bbeacf5b460c9910949f3dba8b0bd
  • ✖ message may not be empty
  • ✖ type may not be empty
• Commit: 1b1c94c9f55c52879e5bc369bdbbc3556e16b354
  • ✖ message may not be empty
  • ✖ type may not be empty
• Commit: 7aa5cafceaf21683e311edf1b1b13bf78e6bdb99
  • ✖ message may not be empty
  • ✖ type may not be empty
• Commit: e20f6facd47c647962ae8191483b4c8f2f570e1a
  • ✖ message may not be empty
  • ✖ type may not be empty
• Commit: 96ea74faec952a8f39096eb1e59daa539d8b1059
  • ✖ message may not be empty
  • ✖ type may not be empty
• Commit: 08f4947b2915a7416617f6f45eef3657651b0edd
  • ✖ message may not be empty
  • ✖ type may not be empty
• Commit: 2fdacfc878679c525d8c6754f543585dda183cc7
  • ✖ message may not be empty
  • ✖ type may not be empty
• Commit: db64c38142a44eeb1cc18ea989080adcb4dfc097
  • ✖ message may not be empty
  • ✖ type may not be empty

You may need to change the commit messages to comply with the repository contributing guidelines.

---

🤖 This comment was generated by commitlint[bot]. Please report issues here.

Happy coding!

[ghost]

There were the following issues with this Pull Request

• Commit: 6a3ab54c390bbeacf5b460c9910949f3dba8b0bd
  • ✖ message may not be empty
  • ✖ type may not be empty
• Commit: 1b1c94c9f55c52879e5bc369bdbbc3556e16b354
  • ✖ message may not be empty
  • ✖ type may not be empty
• Commit: 7aa5cafceaf21683e311edf1b1b13bf78e6bdb99
  • ✖ message may not be empty
  • ✖ type may not be empty
• Commit: e20f6facd47c647962ae8191483b4c8f2f570e1a
  • ✖ message may not be empty
  • ✖ type may not be empty
• Commit: 96ea74faec952a8f39096eb1e59daa539d8b1059
  • ✖ message may not be empty
  • ✖ type may not be empty
• Commit: 08f4947b2915a7416617f6f45eef3657651b0edd
  • ✖ message may not be empty
  • ✖ type may not be empty
• Commit: 2fdacfc878679c525d8c6754f543585dda183cc7
  • ✖ message may not be empty
  • ✖ type may not be empty
• Commit: db64c38142a44eeb1cc18ea989080adcb4dfc097
  • ✖ message may not be empty
  • ✖ type may not be empty
• Commit: 3ece534ea0463e471320947864900210d160dfc7
  • ✖ message may not be empty
  • ✖ type may not be empty

You may need to change the commit messages to comply with the repository contributing guidelines.

---

🤖 This comment was generated by commitlint[bot]. Please report issues here.

Happy coding!