Adding annotations to apps is broken

[epatters]

At one time this worked, but I now get the error:

$ fsh app update myaction myaction.js -a description "My description"
{
  isUsageError: true,
  name: "UsageError",
  message: {
  },
  raw: {
    message: "This command requires 2 parameters, but you provided 9",
[...]

[starpit]

thanks @epatters for the bug report! sorry for the delay, we had a massive power outage, tornados and all. i'll look into this, and make sure it's covered by tests.

[starpit]

@epatters can you provide the output of fsh version thanks

[epatters]

Thanks @starpit, the output of fsh version is 1.4.3.

[starpit]

thanks. hmm, two of us have tried, without success, to duplicate this issue. we'll keep investigating.

[starpit]

which platform are you on? linux? mac? thanks

[epatters]

That's odd. I'm on OS X.

[epatters]

It seems that the words in the description are somehow being treated as arguments. Compare these two invocations:

$ fsh app update welcome welcome.js -a description 'My welcome action'
{
  isUsageError: true,
  name: "UsageError",
  message: {
  },
  raw: {
    message: "This command requires 2 parameters, but you provided 4",
[...]

fsh app update welcome welcome.js -a description 'My welcome action again'
{
  isUsageError: true,
  name: "UsageError",
  message: {
  },
  raw: {
    message: "This command requires 2 parameters, but you provided 5",
[...]

(My original example was adapted from my real actions, so the count of 9 is for a longer description. These two were directly copy-pasted from my terminal.)

[starpit]

Of course! Value with spaces. I'll try it out.

[starpit]

update: it looks like values with spaces work fine from within the graphical shell, but not from the terminal.

[epatters]

Yep, I've been running these commands from the terminal.

[starpit]

ok. i'm on it (and also on tethered internet!). two liner fix coming down the pike! sorry for the oversight.