Add Editor Configs to repo to suggest a consistent code structure

AndrewPaglusch / FlashPaper

One-time encrypted password/secret sharing

MIT License

392 stars 62 forks source link

Add Editor Configs to repo to suggest a consistent code structure #38

Closed mattburchett closed 3 years ago

mattburchett commented 4 years ago

This PR will set the repo to prefer tabs (over spaces), LF over CRLF, and also add some common .gitignore data for the common code editors to prevent fluff in the repo.

This PR also adds a .vscode folder for extension suggestions since EditorConfig isn't respected by VS Code without a plugin.

Matthew-Jenkins commented 4 years ago

I prefer to keep IDE stuff out of a project. Instead document it in the README or something. I personally just use '*' as my gitignore and manually add what I want. Keeps it simple and no accidentally adding possibly confidential info to a repo. Makes the gitignore really easy to understand as well. 'Are we already tracking it? No, then don't add it unless it's forced'