-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
48 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
### 目标 | ||
|
||
- [] 11:00-12:00 typescript | ||
- [] 15:00-16:00 vue3 | ||
- [] 16:30-17:30 英语 | ||
|
||
### 琐碎 | ||
|
||
#### ts | ||
|
||
##### 原生js的隐患 | ||
|
||
1.js的灵活是有代价的 | ||
|
||
2.缺乏文档 | ||
虽然jsDoc提供了类似的功能,但是jsDoc是写在注释中的,随便写也不会报错,而且对于复杂的对象或者函数,jsDoc会非常冗长和笨重,即使你的jsDoc是正确的,当你重构代码时,找到各种函数的jsDoc再重写一遍将非常痛苦(chore n.讨厌的工作) | ||
|
||
3.weaker developer tooling | ||
|
||
<figure> | ||
<blockquote> | ||
<p> | ||
Because JavaScript doesn’t provide built-in ways to identify types, and code easily diverges from JSDoc comments, it can be difficult to automate large changes to or gain insights about a codebase. | ||
</p> | ||
</blockquote> | ||
<figcaption>—Josh Goldberg<cite>Learning TypeScript</cite></figcaption> | ||
</figure> | ||
|
||
### vue3 | ||
|
||
<ClientOnly> | ||
<objectification text="WeakMap与Map,WeakMap经常用于存储哪些只有当key所引用的对象存在时才有价值的信息"></objectification> | ||
</ClientOnly> | ||
|
||
|
||
|
||
### 总结 | ||
|
||
### 明日目标 | ||
|
||
- [] 11:00-12:00 typescript | ||
- [] 15:00-16:00 vue3响应式原理看完 | ||
- [] 16:30-17:30 英语 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters