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
@@ -149,15 +149,15 @@ Removing an input, and then subsequently linearizing the Autobase into an existi
149
149
Future releases will see the addition of 'soft removal', which will freeze an input at a specific length, and no process blocks past that length, while still preserving that input's history in linearized views. For most applications, soft removal matches the intuition behind 'removing a user'.
*`output` must be either a fresh Hypercore or a Hypercore that was previously used as an Autobase output.
157
157
158
158
If `base.outputs` is not empty, Autobase will do 'remote linearizing': `base.view.update()` will treat these outputs as the 'trunk', minimizing the amount of local re-processing they need to do during updates.
Removes an output Hypercore. `output` can be either a Hypercore or a Hypercore key.
163
163
@@ -179,7 +179,7 @@ They should fail in the presence of unavailable nodes -- the deterministic order
179
179
180
180
The simplest kind of linearized view (`const view = base.linearize()`), is just a Hypercore containing the results of a causal stream in reversed order (block N in the index will not be causally dependent on block N+1).
Generate a Readable stream of input blocks with deterministic, causal ordering.
185
185
@@ -191,7 +191,7 @@ If an input node is causally-dependent on another node that is not available, th
191
191
192
192
Similar to `Hypercore.createReadStream()`, this stream starts at the beginning of each input, and does not guarantee the same deterministic ordering as the causal stream. Unlike causal streams, which are used mainly for indexing, read streams can be used to observe updates. And as they move forward in time, they can be live.
Creates a new linearized view, and sets it on `base.view`. The view mirrors the Hypercore API wherever possible, meaning it can be used as a drop-in replacement for a Hypercore instance.
262
262
@@ -271,7 +271,7 @@ When calling `base.start` manually, it must only be called once.
271
271
|**`unwrap`**| Set this to auto unwrap the gets to only return .value | Boolean |`false`|
272
272
|**`apply`**| The apply function described above | Function |`(batch) => {}`|
273
273
274
-
#### **`view.status`**
274
+
#### **`view.status`** {#view.status}
275
275
276
276
The status of the last linearize operation.
277
277
@@ -280,15 +280,15 @@ Returns an object of the form `{ added: N, removed: M }` where:
280
280
*`added` indicates how many nodes were appended to the output during the linearization
281
281
*`removed` indicates how many nodes were truncated from the output during the linearization
282
282
283
-
#### **`view.length`**
283
+
#### **`view.length`** {#view.length}
284
284
285
285
The length of the view. Similar to `hypercore.length`.
0 commit comments