coding best practices proposal

bestPractices.md

Error Handling

Avoid accessing values with multi level path

1. Avoid accessing value from objects directly with more than 2 levels.
2. Defaulting values will results in better error handling.

// Currently
<p>{data.schema.value}</p>
// if schema is undefined, entire UI will not show up.

// Proposed
<p>{data?.schema?.value | ''}</p>
// or 
<p>{data?.schema?.value | 'Invalid Data!'}</p>
// safely renders the UI, and if there is a data error user still be able to revert those changes if possible possible.
// lodash also has some better way to acces this, when there is a complex path.

3. Now, even a small module has an error, entire application will not show up.
4. Now, if such errors occured, user might have to clear the data from pg or to wait for the update.
5. Better error message can be shown only at the place of error. all other modules remains functioning.

Cons

1. We may have to handle analytics by writing extra code. error boundary will not trigger here at all.