Closed rpkoller closed 10 years ago
that is strange. i've built a small test project few minutes ago. there it was possible to switch from -ck to .min and codekit is sticking to it afterwards. thats odd :/
Tried, can confirm this.
The only way I was able to change -ck
to .min
is:
-
to .
, leave the inputc
to m
, leave the inputk
to i
, leave the inputn
, blurBut I don't think it is the proper way to have the field filled :)
hm i've started codekit with a pressed shift key and removed the config.codekit file. then i've made the settings seen on the right which lead to the output seen on the left. :/ quite strange. happened on 10.8.5 and beta 16.
@bdkjones I've tried the described flaw in a small sample project today with the intention to sample the process in the terminal for beta 18. The odd part was it worked in the sample project. Then i've retried it in my main project i am working on right now, where i initially ran into that issue. i've deleted the min js files and tried rewriting them again. What hasn't worked in beta 16 works in beta 18 now even i haven't found anything specifically referring to that issue in the change log. i don't know if for @Andreyco the issue is also gone, but for me it seems it is.
ok have to correct myself it isn't working again. don't know why it did the last time i tried.
@bdkjones the issue still presists even in the final. today i've created a small sample project and ran into the issue @Andreyco described. i finally made it to name it with .min as suffix but see for yourself:
the suffix is set to .min but it writes out -ck anyway. shall i upload the sample project somewhere or is the suffix renaming reproduceable on your side?
am running codekit on 10.8
Did the output file already exist before you made the change to the suffix? If so, CodeKit isn’t going to automatically change the output path; you’ll need to do that manually.
On 9 Mar 2014, at 12:06, Ralf Koller notifications@github.com wrote:
@bdkjones the issue still presists even in the final. today i've created a small sample project and ran into the issue @Andreyco described. i finally made it to name it with .min as suffix but see for yourself:
the suffix is set to .min but it writes out -ck anyway. shall i upload the sample project somewhere or is the suffix renaming reproduceable on your side?
am running codekit on 10.8
— Reply to this email directly or view it on GitHub.
Actually, it doesn’t matter if the output file existed or not. Once the project is added to CodeKit, the output suffix is already set for the output path of each JS file. You need to edit the New Project Defaults BEFORE adding your project to CodeKit. You’ll also need to delete the config.codekit file in each project you’ve already added so that the app uses the global defaults (including the different suffix) when you add those projects to the app.
On 9 Mar 2014, at 15:21, Bryan Jones bryan@incident57.com wrote:
Did the output file already exist before you made the change to the suffix? If so, CodeKit isn’t going to automatically change the output path; you’ll need to do that manually.
On 9 Mar 2014, at 12:06, Ralf Koller notifications@github.com wrote:
@bdkjones the issue still presists even in the final. today i've created a small sample project and ran into the issue @Andreyco described. i finally made it to name it with .min as suffix but see for yourself:
the suffix is set to .min but it writes out -ck anyway. shall i upload the sample project somewhere or is the suffix renaming reproduceable on your side?
am running codekit on 10.8
— Reply to this email directly or view it on GitHub.
ahhhhhhhhhh after changing the default settings things turned much more sane and comprehendible. thanks.
I've tried to enter .min as file suffix
but codekit sticks to -min. is something wrong about .min and codekit prevents me from doing something silly or is it more of a misbehaviour?