Mark Stacey 564f76584b Tolerate missing or falsey substitutions (#8907) ... Previously the `getMessage` function would throw if a substitution was falsey. Now it will accept any substitution, including `undefined`. A substitution of `null` or `undefined` will still be reported to Sentry and printed to the console as an error, but it will not interrupt execution. Any `null` or `undefined` substitutions will be rendered as empty strings. Ideally we'd never pass in `null` or `undefined` as a substitution, but in practice this sometimes just occurs breifly between renders, which isn't a severe enough problem to justify crashing the UI. The detection of React component substitutions has been updated as well, to ensure that `null` values aren't counted as React substitutions.		2020-07-03 13:02:35 -03:00
..
constants	Implement asset page (#8696)	2020-06-01 14:54:32 -03:00
higher-order-components	Refactor confirm approve page (#8757)	2020-06-09 17:10:07 -03:00
utils	Tolerate missing or falsey substitutions (#8907)	2020-07-03 13:02:35 -03:00