Merge ~mpontillo/maas:react--use-vanilla-components into maas:master
Status: | Rejected |
---|---|
Rejected by: | Adam Collard |
Proposed branch: | ~mpontillo/maas:react--use-vanilla-components |
Merge into: | maas:master |
Diff against target: |
405 lines (+93/-77) 7 files modified
Makefile (+3/-1) package.json (+3/-2) src/maasserver/static/js/angular/maas.js (+1/-1) src/maasserver/static/js/react/test.js (+36/-0) src/maasserver/static/partials/domains-list.html (+4/-1) webpack.config.js (+4/-3) yarn.lock (+42/-69) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
MAAS Maintainers | Pending | ||
Review via email: mp+340648@code.launchpad.net |
Description of the change
This branch is an example of how to use React components in MAAS/Angular templates.
The first iteration of this branch used 'react2angular', but the resulting React component was not able to respond to changes that were pushed in by the Angular websocket. The 'ngreact'-based version (the current branch) works for this purpose, but requires more glue code and complexity, and also needs work because it pulls in the version of Angular from npm. MAAS is still using the version of Angular that is in the archive, so this causes it to be loaded twice. (If ngreact were to be used in production, we would need to change the code to only pull in Angular from one location.)