Skip to content

Conversation

@peyton-alt
Copy link
Contributor

entire disable will always write to settings.local.json. If it does not exist, will create one and write to it. When running entire disable without -- project parameter will write to settings.local.json, instead of settings.json when local settings does not exist. If -- project is specified, writes to settings.json

  • entire disable: writes to .entire/settings.local.json (creates if missing)
  • entire disable --project: writes to .entire/settings.json

Expected Behavior:

  • Without --project: Should always write to .entire/settings.local.json, creating it if it doesn't exist
  • With --project: Should write to .entire/settings.json

Change 1 - setup.go: Simplified runDisable to always write to local settings when --project is not specified.
 
Change 2 - setup_test.go: Commented out the old test and added TestRunDisable_CreatesLocalSettingsWhenMissing which verifies:

  • Local settings file is created with enabled: false
  • Project settings remain unchanged (still enabled: true)

…ot exist, will create one and write to it. When running entire disable without -- project parameter will write to settings.local.json, instead of settings.json when local settings does not exist. If -- project is specified, writes to settings.json

- entire disable: writes to .entire/settings.local.json (creates if missing)
- entire disable --project: writes to .entire/settings.json
Entire-Checkpoint: 2a29469db94c
@Soph Soph merged commit 32f02e0 into main Jan 15, 2026
3 checks passed
@Soph Soph deleted the disable-writes-local-settings branch January 15, 2026 11:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants