| Name | Acronym | Type | Lead^/Lag* | tv | mt5 | tt | tc2 | mio | mv | pc | js | js2 | py | py2 | mat |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Absolute Breadth Index | Momentum | ❌ | ❌ | ❌ | ❌ | ✅ | ✅ | ❌ | ❌ | ❌ |
m-ahmadi
/ all-technical-indicators.md
Last active
June 18, 2024 10:56
A List of All Technical Indicators
dance2die
/ Comparison Table.md
Last active
December 22, 2023 23:26
| Short-circuit? | Short-circuits on? | Fulfilled on? | Rejected on? | |
|---|---|---|---|---|
| Promise.all | Yes | First rejected promise | All promise fulfilled | First rejected promise |
| Promise.allSettled | No | N/A | Always | N/A |
| Promise.race | Yes | First settled | First promise fulfilled | First rejected promise |
| Promise.any | Yes | First fulfilled | First promise fulfilled | All rejected promises |
robertpainsi
/ commit-message-guidelines.md
Last active
July 27, 2024 06:17
Commit message guidelines
Short (72 chars or less) summary
More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).
Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages