Skip to content

feat(config), support saving config values in the local workspace/scope #9555

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Feb 13, 2025

Conversation

davidfirst
Copy link
Member

@davidfirst davidfirst commented Feb 13, 2025

Proposed Changes

  • introduce --local flag for bit config set to save the config in the local scope at .bit/scope.json.
  • introduce --local-track flag for bit config set to save the config in the workspace.jsonc.
  • default to save to the global-scope, same as it is now.
  • introduce --detailed flag for bit config list to show the config-stores of all: workspace, scope and global. Separately and combined.
  • introduce --origin flag for bit config list to show the config of a specific store: global, scope or workspace.
  • introduce --json flag for bit config list to print the config in json format.

@davidfirst davidfirst enabled auto-merge (squash) February 13, 2025 22:15
@davidfirst davidfirst merged commit 5b42a14 into master Feb 13, 2025
10 checks passed
@davidfirst davidfirst deleted the feat-local-config branch February 13, 2025 23:21
davidfirst added a commit that referenced this pull request Feb 14, 2025
…le is changed (#9557)

This is a continuation of the recent config changes done in #9555 .

* change the scope-watcher to watch also the scope.json file and
invalidate the scope-store when it changes.
* fix the invalidateCache in all places to get it work with the new
config mechanism.
* remove `teambit.legacy/global-config` component. It's not needed
anymore. the GlobalConfig class has moved to the ConfigStore aspect.
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.

2 participants