Skip to content
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

Can we configure settings in a file under the project? #843

Closed
jpa95 opened this issue May 8, 2024 · 4 comments
Closed

Can we configure settings in a file under the project? #843

jpa95 opened this issue May 8, 2024 · 4 comments

Comments

@jpa95
Copy link

jpa95 commented May 8, 2024

Apologies if this has been asked or if it is already possible; i could not find it.

Basically I am hoping that TODO Tree could look for a config file in the current project folder, as do many other extensions such as editor.config and prettier.

Having the configuration in the VS Code settings (regardless of project/user/workspace level) make it impossible to share TODO-Tree config between developers on the same project easilly. In our environment, Ideally a developer would pull the configuration for all extensions as part of the code on git,.

Regards,
Joel

@lasseba
Copy link

lasseba commented May 29, 2024

Just want to second that idea...
If we use TODO tree actively in the project, it is quite vital all have the same settings.

@DaveParr
Copy link

We've solved this by configuring the settings at the workspace level in the .vscode/settings.json (both by editing the file and using the GUI). That file is then commited to git, and when the project is cloned the file comes down with it. Might that work for you @jpa95?

@jpa95
Copy link
Author

jpa95 commented Oct 10, 2024

Since i asked this question we have started working with Workspaces (abc.code-workspace) and have put the todo tree config in there. So yeah, using workspaces was the way to go for us. For other extensions there are still some settings that need to be inidivual to the developer (user settings), but most of our settings are now shared by the *.code-workspace files that we commit into git. Thanks for the reply @DaveParr!

@jpa95 jpa95 closed this as completed Oct 10, 2024
@DaveParr
Copy link

No problem @jpa95 , glad it's all working :)

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

No branches or pull requests

3 participants