Add more required types or explanation of limits to not adding fields #606
robindunkerley
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Issues
it is not clear to developers that the
lineItemfield must be included on the invoice object to avoid validationException errors.It is not clear that the
accountCodefield must be included on thelineItemobject in order to create invoices with a status ofInvoice.StatusEnum.AUTHORISEDwithout experiencing validationException errors.In order to send invoices using the
emailInvoicemethod, invoices must have a status ofInvoice.StatusEnum.AUTHORISED. This is not clear in and of itself, however, a solution to issue 2 would reduce unclear errors for developers.Suggested solutions
Make
lineItema required field on typeInvoice.Make
accountCodea required field on typelineItemOR include an explanatory comment inlineItem.d.tshighlighting its relation to adding a status of authorised.Beta Was this translation helpful? Give feedback.
All reactions