# `affects`
Forces linked blocks to be edited together. If you change this block and leave the block it points at untouched, the run
fails.
## Syntax
| `affects` | `file:name`, or `:name` for the same file | — |
Separate multiple targets with commas:
```rust
// <block affects="README.md:supported-langs, docs/api.md:languages">
```
## Example
**src/lib.rs**:
```rust
// <block affects="README.html:supported-langs">
pub enum Language {
Rust,
Python,
}
// </block>
```
**README.html**:
```html
<ul>
<li>Rust</li>
<li>Python</li>
</ul>
```
Modify the enum and BlockWatch fails until you also touch `supported-langs` in `README.html`.
## Direction
`affects` is one-way. The example above catches "code changed, docs didn't" — but not the reverse. For two-way drift
detection, name both blocks and point each at the other:
```rust
// <block name="languages-code" affects="README.html:supported-langs">
```
```html
```
## Notes
- **Diff mode only.** Without a diff on stdin every block counts as unmodified, so `affects` can never fire. Pipe
`git diff --patch | blockwatch` to use it. If you want a check that also works on a full-tree run, use [
`same-as`](same-as.md).
- **Co-editing, not agreement.** `affects` only checks that both sides were touched — it does not compare their
contents. Touching the target with an unrelated edit satisfies it. When the two blocks should hold the same *value*, [
`same-as`](same-as.md) is the stronger check.
- **Missing targets are violations.** A reference to a `name` that does not exist is reported.
- Combining `affects` with [`check-lua`](check-lua.md) gives a script access to the affected blocks' contents through
`ctx.affects`, which is a way to compare them without file IO.
---
← [Validators](README.md) · [README](../../README.md)