Mark Stacey 59a1746afc Validate custom spend limit (#7920) ... The custom spend limit was previously not validated. It did have a minimum of zero set, but this didn't have any affect (that minimum is used for form constraint validation, and this field wasn't in a form). The field was never checked to ensure the contents didn't exceed the maximum. The field is now checked for values that exceed the maximum, and invalid values in general (including negative values). The parameters to the `showEditApprovalPermissionModal` were also alphabetized to make them easier to read. In the course of doing this, I noticed that the origin was missing from one of the calls. This was responsible for the modal saying "Spend limit requested by undefined" when clicking "Edit" under the transaction details. This has been fixed.		2020-01-29 14:16:38 -04:00
..
app	Validate custom spend limit (#7920)	2020-01-29 14:16:38 -04:00
lib	Remove unnecessary get environment type parameter (#7891)	2020-01-24 15:12:58 -04:00
index.js	Fix batch transaction UX (#7473)	2020-01-10 06:34:02 -08:00