robhrt7 / backbase-widget-dependencies-proposal Goto Github PK

Current proposal is not fully compatible with todays Backbase CXP structure, first implementations will have differences in implementation as any transition stages do.

Our goal for now, is to create flexible core. Compatibility layers will be described in separate documents, and will be treated as temporarily solutions till global refactorings.

assets-tree.json, that could be generated during backbase-cli install may be very useful for developing build scripts on project level. It will look approximately like this:

{
"bower_components" : {
  "jquery": {
    "js": "dist/jquery.js"
  }
},
"bb_components" : {
  "widget-robert-todo": {
    "js": "js/robert-todo.js",
    "css": "css/robert-todo.css"
  }
}
}

How do you think, will it be really useful, or we could just parse dependencies folders by hand from our project build scripts?

Is it worth it to maintain in official backbase-cli install tool?

As Bower allows to configure names, folder naming topic is open for discussion. Current proposal describes two endpoints for dependencies:

• bower_components - standard Bower path for storing client-side dependencies
• bb_components - backbase structure related folder for item dependencies (widgets, bundles, containers, etc...)

I suggest using standard directory for client-side dependencies, as in most open source projects in is not renamed. Despite the ability to configure, it's not always easy to follow conf changes, also as config for Bower is defined in .bowerrc, most users will not see it at all (dotfiles are hidden by default).

In case with item deps - bb_components, I chose temp name, so I would like to hear your options.