You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do not know if this could be a possible enhancement. Basically, how explained into the documentation, about Custom Config, we can define a ovverriden configuration, providing an overridePath. For my understanding, I saw that even if the overridePath is defined, the plugin reads all tasks within configPath folder, loading all tasks found there, and then the ones defined in overridePath folder.
An enhancement would be: let's suppose that overridePath and configPath are defined. Before to load all tasks within configPath folder, IF a certain tasks (for example jshint.js) exists within overridePath, THEN do not load the jshint.js task which eventually lives within configPath folder.
In other terms, we are giving precedence to the overridePath tasks over the configPath ones.
I hope to have been clear :)
The text was updated successfully, but these errors were encountered:
brunano21
changed the title
Enhancement
Enhancement: not load tasks from configPath if same task within overridePath exists
May 22, 2015
Hi all!
I do not know if this could be a possible enhancement. Basically, how explained into the documentation, about Custom Config, we can define a ovverriden configuration, providing an
overridePath
. For my understanding, I saw that even if theoverridePath
is defined, the plugin reads all tasks withinconfigPath
folder, loading all tasks found there, and then the ones defined inoverridePath
folder.An enhancement would be: let's suppose that
overridePath
andconfigPath
are defined. Before to load all tasks withinconfigPath
folder, IF a certain tasks (for example jshint.js) exists withinoverridePath
, THEN do not load the jshint.js task which eventually lives withinconfigPath
folder.In other terms, we are giving precedence to the
overridePath
tasks over theconfigPath
ones.I hope to have been clear :)
The text was updated successfully, but these errors were encountered: