Skip to content

Comments

refactor: remove enabled field from fugitive/neogit config#126

Merged
barrettruth merged 1 commit intomainfrom
refactor/implicit-integration-enabled
Feb 16, 2026
Merged

refactor: remove enabled field from fugitive/neogit config#126
barrettruth merged 1 commit intomainfrom
refactor/implicit-integration-enabled

Conversation

@barrettruth
Copy link
Owner

Problem

Users had to pass enabled = true or enabled = false inside
fugitive/neogit config tables, which was redundant — table presence
already implied the integration should be active.

Solution

Remove the enabled field from the public API. Table presence now
implies enabled, false disables, true expands to sub-defaults.
The enabled field is still accepted for backward compatibility.

Added 20 compute_filetypes tests covering all config shapes (true,
false, table, nil, backward-compat enabled field). Updated docs
and type annotations.

@barrettruth barrettruth force-pushed the refactor/implicit-integration-enabled branch from 264c8d8 to 3be4a47 Compare February 16, 2026 00:39
Problem: users had to pass `enabled = true` or `enabled = false` inside
fugitive/neogit config tables, which was redundant — table presence
already implied the integration should be active.

Solution: remove the `enabled` field from the public API. Table presence
now implies enabled, `false` disables. `true` expands to sub-defaults.
The `enabled` field is still accepted for backward compatibility:
`{ enabled = false }` collapses to `false`, and `enabled = true` or nil
strips the field silently. Default config changed from
`{ enabled = false, ... }` tables to just `false`. Added 20
compute_filetypes tests covering all config shapes. Updated docs.
@barrettruth barrettruth force-pushed the refactor/implicit-integration-enabled branch from 3be4a47 to bd7a44a Compare February 16, 2026 00:41
@barrettruth barrettruth merged commit cbc93f9 into main Feb 16, 2026
7 checks passed
@barrettruth barrettruth deleted the refactor/implicit-integration-enabled branch February 16, 2026 00:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant