4 ms·
I'd suggest having them in a directory just called config/ On having it start with a dot: Why? Why would we pretend that these crucial files don't exist? On h
by paulhodge 3y ago
I'd suggest having them in a directory just called config/
On having it start with a dot: Why? Why would we pretend that these crucial files don't exist?
On having it named meta: These files aren't "about" the project or "above" the project, they ARE the project.
- fallat 3y agoYeah hiding these files would be a huge mistake.
- benatkin 3y agoand security problem. whoops, just committed all the secrets in .meta/.env.production!
- CuriousCosmic 3y agoThank god when you commit, the editor lists all the files you've committed in the comments of the commit message.
- phanimahesh 3y agoWhat editor? There's no editor in git add . && git commit -am "made changes" /s
- CuriousCosmic 3y agohooo boy. i could feel my blood pressure spike for a brief moment before i saw the `/s`.
- ks2048 3y agoYes, but why would anyone follow this very reasonable line of thinking if you don't have a custom domain name to back it up?
- 111111IIIIIII 3y agoOr hide them with your IDE if they disturb you so much
- activiation 3y ago~/.config is already a thing
- deleted 3y ago[deleted]
- sph 3y agoIt's not configuration though. Specifically, it's not configuration of the project in question, it's configuration for third party accessories. If I'm writing an editor, I expect the config directory in the source code to hold the configuration for the editor, not .babelrc meta is a much better name and they are "about" the project, not the project itself, so I disagree on that point. Though I agree it should not be hidden. I will start having a "meta" directory in my projects
- paulhodge 3y agoBut third party accessories are an essential part of any project these days, they aren't optional or afterthoughts. In that page they mention docker-compose.yml as once example. Most likely it's impossible (in its current state) to actually run that application without Docker. Other things that would land in the folder: - Files essential to building the project - Files essential to running the test suite - Files essential to developing on the project IMO a "project" includes all those things. In your definition are those all "meta"? Does "meta" mean anything that's not source code?