Review our components for how they handle falsy value for their nunjucks options expecially if they make a diffence between null, undefined, false,0, ''. If there is a difference between falsy values or a specific reason not to make a difference, check if there are tests verifying the components' rendering for these nuances.
Why
This will make our code more resilient in the case of minor refactors that change how we handle falsy component options (eg, using Nunjucks' default filter instead of if <VALUE>), limiting the risk of us introducing bugs.
Who needs to work on this
Developers
Who needs to review this
Developers
Done when
[ ] All components have been reviewed for their falsy options
[ ] Results of the review have been documented (in a spreadsheet or similar)
What
Review our components for how they handle falsy value for their nunjucks options expecially if they make a diffence between
null
,undefined
,false
,0
,''
. If there is a difference between falsy values or a specific reason not to make a difference, check if there are tests verifying the components' rendering for these nuances.Why
This will make our code more resilient in the case of minor refactors that change how we handle falsy component options (eg, using Nunjucks'
default
filter instead ofif <VALUE>
), limiting the risk of us introducing bugs.Who needs to work on this
Developers
Who needs to review this
Developers
Done when