(commit): moved cache (#240)

[dealloc]

Moved the cache from the home folder to a designated config folder

This fixes #240 by moving the commitizen.json cache file out of the home folder

[LinusU]

I think that the convention is that initial uppercase letter is for classes, can you change this name to configDir instead? thanks

[dealloc]

Certainly, hang on :)

[dealloc]

@LinusU I don't see why the builds should fail, could this be related to #205 ?

[LinusU]

👍 I'll look into the failing build when I'm not at work

[dealloc]

I'm pulling my hairs out over this one, I literally replaced a string with another string ?_?

[jimthedev]

@dealloc @LinusU I could be wrong, but I am pretty sure this is failing simply because if the directory doesn't exist, it isn't being created first. Your PR should probably create that directory before trying to create the file.

[dealloc]

I'm going to give that a try

[LinusU]

@dealloc Maybe it's better to use this package since it's actually meant for cache? The current one is meant for config which isn't really what this is...

https://www.npmjs.com/package/cachedir

[dealloc]

does this also handle creating the directories etc? or would I need to handle that myself?

EDIT: a quick skim gives me the impression this more or less does the same as the package you suggested before (generate OS specific strings) but it seems that this package will throw on Windows, which is probably not really what we want

[LinusU]

This works the same, it will just give back the path.

Ahh, you're right, we should probably fix that first. PR welcome if you have the time, otherwise I'll try and fix it as soon as possible.

[dealloc]

I suggest for now we could just use the package I already included and just update it when the other one is fixed. The main thing right now is that it won't commit and I have no clue why (I suspect #205 is the culprit here).