-
Notifications
You must be signed in to change notification settings - Fork 72
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
chore: ignore vscode settings #1444
chore: ignore vscode settings #1444
Conversation
This is for developing as it will allow integration tests (hidden behind the feature flag) to be indexed by RA
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to add editor configs to the repo? I'm always on the fence about this. Maybe we should add the .vscode
to .gitignore
instead, then you won't be bugged about having a new file.
I wager most Devs use VSCode and if they are going to work on tests this is a must. Also for me if I move to a new computer I prefer to have this already there. It's a small file that doesn't affect other editors. But if there are strong opinions I'm fine having to copy and paste this to each time I set up. |
On second thought devs might want to edit it so I just did |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
it
feature to rust-analyzer in vscode
I highly recommend the Rust Feature Toggler extension if you aren't using it. It provides a status bar UI for toggling whether a feature is enabled or not in a rust project. |
This is for developing as it will allow integration tests (hidden behind the feature flag) to be indexed by RA.
It also ignores all future edits to the file.