Skip to content

Commit 50850a9

Browse files
committed
Fix unorganized list in Objects section
1 parent 50e5c1b commit 50850a9

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

README.md

+8-8
Original file line numberDiff line numberDiff line change
@@ -885,13 +885,13 @@ using getters and setters to access data on objects is far better than simply
885885
looking for a property on an object. "Why?" you might ask. Well, here's an
886886
unorganized list of reasons why:
887887

888-
1. When you want to do more beyond getting an object property, you don't have
888+
* When you want to do more beyond getting an object property, you don't have
889889
to look up and change every accessor in your codebase.
890-
2. Makes adding validation simple when doing a `set`.
891-
3. Encapsulates the internal representation.
892-
4. Easy to add logging and error handling when getting and setting.
893-
5. Inheriting this class, you can override default functionality.
894-
6. You can lazy load your object's properties, let's say getting it from a
890+
* Makes adding validation simple when doing a `set`.
891+
* Encapsulates the internal representation.
892+
* Easy to add logging and error handling when getting and setting.
893+
* Inheriting this class, you can override default functionality.
894+
* You can lazy load your object's properties, let's say getting it from a
895895
server.
896896

897897

@@ -922,11 +922,11 @@ class BankAccount {
922922
this._balance = amount;
923923
}
924924
}
925-
925+
926926
get balance() {
927927
return this._balance;
928928
}
929-
929+
930930
verifyIfAmountCanBeSetted(val) {
931931
// ...
932932
}

0 commit comments

Comments
 (0)