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
yogi has init which builds the directory structure that is required. For shifter, it by default, also expects the same directory structure.
For example, it expects my javascript files to be in js, so, in my builder.json, it expects me to use the following if I my test-module.js is in the same folder as builder.json:
"jsfiles": [
"../test-module.js"
]
instead of (relative to builder.json):
"jsfiles": [
"test-module.js"
]
Since shifter expects a certain directory structure, I think it would be beneficial to have shifter able to generate the directory for us using an init command. This is especially useful for yui projects that are folders within a larger and more complex project and already use git in the root. Yogi, forces us to have a git at the top level for our modules, otherwise it refuses to run init, so shifter is a better fit for projects like this.
The text was updated successfully, but these errors were encountered:
yogi has init which builds the directory structure that is required. For shifter, it by default, also expects the same directory structure.
For example, it expects my javascript files to be in
js
, so, in mybuilder.json
, it expects me to use the following if I mytest-module.js
is in the same folder asbuilder.json
:instead of (relative to
builder.json
):Since shifter expects a certain directory structure, I think it would be beneficial to have shifter able to generate the directory for us using an
init
command. This is especially useful for yui projects that are folders within a larger and more complex project and already use git in the root. Yogi, forces us to have a git at the top level for our modules, otherwise it refuses to run init, so shifter is a better fit for projects like this.The text was updated successfully, but these errors were encountered: