You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-**Use `### Example` instead of `@example`** - for better markdown rendering and consistency
121
121
-**Write clear descriptions** - explain what the function does, not how to use it
122
122
-**Use `{@link}` for references** - link to types, interfaces, functions, and exported symbols on first mention for discoverability
123
+
-**Avoid pipe characters in first sentence** - TypeDoc extracts the first sentence for table descriptions, and pipe characters (even in inline code like `T | undefined`) break markdown table rendering. Move such details to subsequent sentences.
Copy file name to clipboardExpand all lines: apps/web/src/app/(docs)/docs/library/page.mdx
+18-14Lines changed: 18 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ export const metadata = {
6
6
7
7
# Get started with the library
8
8
9
-
This guide will get you up and running with Evolu Library.
9
+
This guide will help you get started with the Evolu Library.
10
10
11
11
<Note>
12
12
Requirements: `TypeScript 5.7` or later with the `strict` flag enabled in
@@ -21,32 +21,36 @@ npm install @evolu/common
21
21
22
22
## Learning path
23
23
24
-
We recommend learning Evolu Library in this order:
24
+
We recommend learning the Evolu Library in this order:
25
25
26
-
### 1. Result – Error handling
26
+
### 1. Array
27
27
28
-
Start with [`Result`](/docs/api-reference/common/Result/type-aliases/Result), which provides a type-safe way to handle errors without exceptions. It's the foundation for composable error handling throughout Evolu.
28
+
Start with [`Array`](/docs/api-reference/common/Array), which provides helpers for improved type-safety and developer experience.
29
29
30
-
### 2. Task – Asynchronous operations
30
+
### 2. Result
31
31
32
-
Learn [`Task`](/docs/api-reference/common/Task/interfaces/Task), which represents asynchronous computations in a lazy, composable way.
32
+
Learn [`Result`](/docs/api-reference/common/Result/type-aliases/Result), a type-safe way to handle errors. It's the foundation for composable error handling.
33
33
34
-
### 3. Type – Runtime validation
34
+
### 3. Task
35
35
36
-
Understand the[`Type`](/docs/api-reference/common/Type) system for runtime validation and parsing. This enables you to enforce constraints at compile-time and validate untrusted data at runtime.
36
+
Continue with[`Task`](/docs/api-reference/common/Task/interfaces/Task)for structured concurrency (promises that can be aborted, monitored, and do not leak).
37
37
38
-
### 4. Dependency injection
38
+
### 4. Type
39
39
40
-
Explore the [dependency injection pattern](/docs/dependency-injection) used throughout Evolu for decoupled, testable code.
40
+
Check the [`Type`](/docs/api-reference/common/Type) to enforce constraints at compile-time and validate data at runtime.
41
41
42
-
### 5. Resource management
42
+
### 5. Dependency injection
43
43
44
-
Learn [resource management](/docs/resource-management) with `using`, `DisposableStack`, and how it integrates with `Result` for reliable cleanup.
44
+
Explore [dependency injection](/docs/dependency-injection), the pattern Evolu uses to swap implementations and simplify testing.
45
45
46
-
### 6. Conventions
46
+
### 6. Resource management
47
+
48
+
See [resource management](/docs/resource-management) — `using`, `DisposableStack`, and how it integrates with `Result` for reliable cleanup.
49
+
50
+
### 7. Conventions
47
51
48
52
Review the [Evolu conventions](/docs/conventions) to understand the codebase style and patterns.
49
53
50
54
## Exploring the API
51
55
52
-
After understanding the core concepts, explore the full API in the [API reference](/docs/api-reference/common). All code is commented and test files are written to be read as examples—they demonstrate practical usage patterns and edge cases.
56
+
After understanding the core concepts, explore the full API in the [API reference](/docs/api-reference/common). All code is commented, and tests are written to be read as examples—they demonstrate practical usage patterns and edge cases.
0 commit comments