# `PartActions.find`

> Contract 2.0.0 · package sha256 `a857eca95b35921109faf997094bb4192f12527d9d0fcd4be7e97f06425bad6e` · generated from `configurator-runtime.d.ts` by `services/onsite-scripter/scripts/build-contract-docs.mjs`; edit the source, not this file.

Method of [`PartActions`](PartActions.md) · inherited by [`Query`](Query.md), [`Parts`](Parts.md), [`Part`](Part.md) · stable · since 2.0.0 · called as `session.node(nodeId).find`

```ts
find(query: Query): Parts<C>;
```

Searches inside these parts. Sync; the same rules as [`Writer.find`](Writer.find.md), except for a write: a
Query has no "inside this part" form, so `set()` through the result writes one rule per part
it matches at the call, each bound to that part's address as a write through that [`Part`](Part.md)
(spec section 6.10, R3; no match: 'target-unmatched' at once). A part that matches only later
gets none: for that, write a top-level query (`node`, `collection` and `key` scope a model, a
collection and an item).

## Generic-API test (spec 3.1)

| Rule | Result |
| --- | --- |
| 1. Neutral name | pass: `find` names no product |
| 2. A precedent | not recorded: no ledger row (coverage.json) names this member or its owner |
| 3. Two apps, or labs | not recorded: no ledger row names this member or its owner |
| 4. The cheaper fix first | not recorded per member (Appendix B decides it per need) |