Closed Subterrane closed 8 years ago
Yep. I don't like invisible files. .jshintrc
, .travis.bullshit
, .whatthefuckisyml.yml
, etc. The visibility of the file lets you quickly identify folders that are CodeKit projects when you're browsing around. If I hid the file, folks would complain that sometimes when they add folders the files in there don't adopt the defaults they set in the app, etc. For those reasons, I leave the file visible.
I've changed my mind. I think you have a good point.
Correct me if I'm wrong, but I should probably check the config file into git. When I checkout a different branch, it should update the corresponding config file and CodeKit will notice the change and load the new one, right? Then when I switch back to the previous branch, the config changes and CodeKit reloads again, correct?
Or am I being dumb?
@Subterrane indeed you should. But do not forget to pause file-watching while checking out as with CK2. Further reading
While we're at the config-file topic: in CK2 the config file is also visible, but not visible in CK itself. At first I thought it was a bug, that I can process my config file in CK3, but everything works fine.
I think it would be cleaner if the file was not visible in CK. Or are there benefits that I'm not seeing?
While we're at the config-file topic: in CK2 the config file is also visible, but not visible in CK itself. At first I thought it was a bug, that I can process my config file in CK3, but everything works fine.
I think it would be cleaner if the file was not visible in CK.
Agreed. I just ran into this.
I thought it was a bug. Is it a bug?
Quick, short summary:
codekit3.config
stares at me.Expected results: Seems like the filename should start with a
.
so I won't see it.Actual results: It sits in with the rest of my site files because I'm too lazy or stupid to use a source folder.