-
Notifications
You must be signed in to change notification settings - Fork 1.4k
(WIP) Implement application decoupling #959
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Implements the application decoupling as discussed in #913.
Excludes karma.conf.js, protractor.conf.js and test-main.js from the copy build task, so that those files will not be copied over to /dist/** directory. Furthermore also excludes the tsconfig.json from this copy process, as it was copied over before too.
Updates the protractor configuration and associated gulp task.
Adds a e2e.singleRun gulp task to the gulpfile to leave the script in the package.json more compact. Also updates the README to include the new folder and file structure.
- Implements the application decoupling as discussed in #913. - Excludes karma.conf.js, protractor.conf.js and test-main.js from the copy build task, so that those files will not be copied over to /dist/** directory. Furthermore also excludes the tsconfig.json from this copy process, as it was copied over before too. - Updates the protractor configuration and associated gulp task. - Adds a e2e.singleRun gulp task to the gulpfile to leave the script in the package.json more compact. Also updates the README to include the new folder and file structure.
Updates the package.json and gulpfile.ts to fix the issue of running the e2e.singleRun task
Adds a separate package.json for the sources in src/browser.
@@ -0,0 +1,24 @@ | |||
{ | |||
"name": "angular2-seed", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need a new name here?
Hey guys, i now added the separate Looking for input and help here :) // cc @mgechev @ludohenin @d3viant0ne @NathanWalker @Shyam-Chen |
@@ -13,8 +13,9 @@ | |||
"build.test": "gulp build.test --color", | |||
"build.test.watch": "gulp build.test.watch --color", | |||
"generate.manifest": "gulp generate.manifest --color", | |||
"e2e": "protractor", | |||
"e2e.live": "protractor --elementExplorer", | |||
"e2e": "protractor src/browser/protractor.conf.js", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The angular dependencies here should be dropped. Doesn't seem required.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we then also drop the whole "dependencies": { ... }
section in the root package.json
, since this has moved to the src/browser/package.json
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah
@TheDonDope Curious the latest status here? Do you currently need help or have questions at this point? |
Hey @NathanWalker,
Yet, though those 2 open tasks may sound straightforward, there is a bit more to it than it may sound. The branch Thanks! |
Ok @TheDonDope thanks for update, I'll see if I can take a look at some point this week. |
@TheDonDope - I'm picking up the last two tasks on the list. I'll PR the changes into the issue/913-application-decoupling branch |
@d3viant0ne Thank you very much!!!!!!!! |
@d3viant0ne and I are working on this together and plan to have a new PR ready here: https://github.com/DeviantJS/angular2-seed/pull/4 and complete for this by Friday night EST (at which time we will close this one in favor of the other), just fyi |
@NathanWalker sounds awesome! Thanks for the help! We're looking forward to merge your work! |
@mgechev Still working through the configuration, need to loosen completion estimate but hoping for this weekend. |
@d3viant0ne, @NathanWalker: Is there anything i can help you with? I saw there was a merge on your forks Greetings |
@TheDonDope I must report that the decoupling presents problems with SystemJS. More than are likely worth it. We are experimenting in a private project at the moment. |
I honestly just don't see a point in doing it. It's only going to serve to increase both complexity and fragility with at best, limited returns |
@NathanWalker @d3viant0ne |
@TheDonDope - I'm sure it's feasible but the implementation adds more complexity than it removes which kind of defeats the purpose. |
@d3viant0ne so after doing research you found out that the introduced complexity is not worth the decoupling that we're going to get? What is the exact problem with SystemJS that prevents us from finishing the restructuring? |
This PR continues #926, pushing the commits to this repositories own branch (
issue/913-application-decoupling
). It was rebased on the currentmaster
. Below is the original description including the last open tasks:The PR is still a a work in progress:
src/client
tosrc/browser
<- IFbrowser
is now fine for everyone :D I could change it if you wantkarma.conf.js
tosrc/browser/karma.conf.js
test-main.js
tosrc/browser/test-main.js
protractor.conf.js
tosrc/browser/protractor.conf.js
$ npm start
is still running fine (updateseed.config.ts
)$ npm test
is still running fine (updating the paths inkarma.start.ts
,karma.conf.js
andtest-main.js
karma.conf.js
,protractor.conf.js
andtest-main.js
from the copy process todist/**
$ npm run webdriver-start && $ npm run serve.e2e && $ npm run e2e
still runs fine should work now with the updates of commit 4b2ca0bpackage.json
insrc/browser
dist/browser/dev|prod|test|tmp
directoriesAny feedback/help/change requests are welcome as always :)
Have a nice day!