datrinh

Evan Clean Code

“Clean code reads like well-written prose” - Grady Brooch

“Clean code always looks like it was written by someone who cares” – Michael Feathers

“You know you are working on clean code when each routine you read turns out to be pretty much what you expected” – Ward Cunningham

General Rules

datrinh

General

• Use data-test attributes as selectors for testing. Those should not change even when the name/id changes as long as the logic stays the same. This will make tests more robust to changes in the code.

Unit Tests

• Introduction to Vue + Jest: https://vue-test-utils.vuejs.org/guides/#testing-single-file-components-with-jest
• Testing Caveats with VeeValidate: https://logaretm.github.io/vee-validate/advanced/testing.html

Do

datrinh

Identity, Accounts and DID

Get AccountId from Identity

runtime.verifications.getOwnerAddressForIdentity(toAccount);

Get Identity from DID

runtime.did.convertDidToIdentity(did)

datrinh

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules