Remove legacy global config path and its related code
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 474
- Avg merge
- 23h 30m
- Merged PRs (30d)
- 53
Description
As part of https://github.com/netlify/cli/pull/1725 we've added a new per OS global config directory. To minimise impact we've agree on not deleting the legacy global config ~/.netlify/config.json but instead use it as a default value, backing it up to the new directory with all the new changes being reflected in there afterwards.
This issue is to cover the tech debt work of figuring out a strategy to remove those legacy configs and the code related to it:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing PR #1725 and the legacy handling in src/utils/get-global-config.js and src/lib/settings.js. Determine a safe strategy for removing ~/.netlify/config.json support and its related code, including what migration behavior must remain. Done means the legacy configuration path and obsolete code are removed without disrupting the new per-OS global configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100