Closed onlyskyguy closed 8 years ago
Using gulpfile_paths
won't break Sublime Gulp in other projects because it just appends the paths and searches there.
I had the idea of settings per project but I am not sure how to implement it yet, do you have any ideas?
Is there a way to export plugin settings into the main settings file for sublime? I know you can set those in your project (edit project,) On Sep 17, 2015 6:40 AM, "Nicolás Santángelo" notifications@github.com wrote:
Using gulpfile_paths won't break Sublime Gulp in other projects because it just appends the paths and searches there.
I had the idea of settings per project but I am not sure how to implement it yet, do you have any ideas?
— Reply to this email directly or view it on GitHub https://github.com/NicoSantangelo/sublime-gulp/issues/49#issuecomment-141090242 .
Not that I'm aware of, I'm afraid. I think the best you can do is:
1) Add an object for each project name on the Sublime Gulp settings with the keys you want, like
{
// Default settings here
"my_project_name": {
"setting1": 1,
// etc
}
}
2) Add a config file in the root of each project (like a .jshintrc
file).
I think the second one could be the answer given that Sublime Gulp already writes a file to the root of each project (.subilme-gulp.cache
). But I'm not sure.
Well I'm going to go with using the .sublime-project
files (using Edit project
).
It might not be the optimal solution because you don't necessarily need a project to use Sublime, but I think it's best to keep the config files to a minimum.
So the idea is, you can set your Sublime Gulp settings in this order:
"settings" object on sublime-project -> "Gulp" object inside .sublime-project (ST3 only) -> User - Gulp settings -> Default Gulp settings
What do you think? (I'll let you know here when is up)
I think that's great. For any project that you're going to open up repeatedly and use gulp with, putting the settings in sublime project file would take care of a nice workflow. On Sep 20, 2015 9:04 AM, "Nicolás Santángelo" notifications@github.com wrote:
Well I'm going to go with using the .sublime-project files (using Edit project). It might not be the optimal solution because you don't necessarily need a project to use Sublime, but I think it's best to keep the config files to a minimum.
So the idea is, you can set your Sublime Gulp settings in this order:
"settings" object on sublime-project -> "Gulp" object inside .sublime-project (ST3 only) -> User - Gulp settings -> Default Gulp settings
What do you think? (I'll let you know here when is up)
— Reply to this email directly or view it on GitHub https://github.com/NicoSantangelo/sublime-gulp/issues/49#issuecomment-141803365 .
This is up on v5.2.0
! (sorry for the delay, I'm not having a lot of free time)
Please let me know if it works for you or if you have any other ideas or requests.
I'll close this but we can re-open it if you have any problems.
Thanks again!
I have a project which doesn't have a gulpfile in the root directory. Instead its in a nested directory: ex) ProjectRoot/App/gulpfile.js
Is there a way to tell sublime-gulp the location of this gulpfile on a per project basis?
Otherwise, if I change the setting "gulpfile_paths": [], won't this break the path for other projects?