Should msatoshi = 0 be allowed when calling invoice?

[Sword-Smith]

Right now mastoshi can be set to zero and this gives a different amount value/different invoice than if you create an invoice with any as amount. This results in invoices like (from the test net)

lntb01pweh95ppp5g6v4fjnrnd3rfcg7c4na4ptzgaj3kj5krqkv8e8xhw7gac6dya8qdqqxqyjwdkcqp2tz7mm6mdy293eh2wa7gtvs2nc9p60ry2jspanujznduj78u8m8hjte73sztat2ddhs6602xk3e9ra5qz3pxxevm9wtv3nnyaz0mgqdsp42cufu

This seems to not follow the Bolt11 specification which dictates:

A writer:
MUST encode amount as a positive decimal integer with no leading 0s.

[darosior]

AFAICT this is not possible anymore:

$ lcreg1 invoice 0 xxx 'this is a zero-amount invoice.'
{
   "code": -32602,
   "message": "msatoshi: should be positive msat or 'any': invalid token '0'"
}

Can we close this ?