Skip to content
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

Adds improved ember build --watch and tests. #1131

Closed

Conversation

dsawardekar
Copy link
Contributor

This is ember build --watch take 3.

  • options.watch => --watch flag, which is false by default.
  • Build command chooses the task based on options.watch.
  • Watch Task is in build-watch.js.
  • Unit test in cli-test.js verifies that watch option is passed correctly.
  • Acceptance test in smoke-test-slow.js, verifies that changes to file
    are written to rebuilt file by --watch.

}
}
})
.catch(function() {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets remove this unused catch (or use it).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps the catch is needed because of the process.kill (if that is why, can you just leave a small comment)?

@rwjblue
Copy link
Member

rwjblue commented Jun 22, 2014

This is exactly what I was envisioning! Sorry for not being clearer on the earlier feedback, but I'm very happy with how this has progressed.

I left a handful of notes (small things), and we definitely will need an entry in the CHANGELOG for this. Happy to merge once those things are squared away.

landonwilkins and others added 16 commits June 22, 2014 21:35
can't have that!
v0.0.1 had the problem of displaying fail image for both fail and success case.
Prior to this change, only the first item in the directory would be
removed (oops).
* Refactors express server to explicitly start the http server. This was
  what it does naturally, but we need access to the raw server to be
  able to teardown the server between tests.
* Refactor express server to make it a bit more testable.
* Add `addon.serverMiddleware` callback function.  The addon is called
  with the instance of the express app.
* Refactor `api-stub` blueprint (and expected API) so that the express
  app is started in a consistent way. Prior to this, if you had a
  `./server/` folder, your code would create the `express` app add the `ember-cli`
  middleware.
* options.watch => --watch flag, which is false by default.
* Build command chooses the task based on options.watch.
* Watch Task is in build-watch.js.
* Unit test in cli-test.js verifies that watch option is passed correctly.
* Acceptance test in smoke-test-slow.js, verifies that changes to file
  are written to rebuilt file by --watch.
@dsawardekar
Copy link
Contributor Author

Ok will make the changes and update.

@rwjblue
Copy link
Member

rwjblue commented Jun 22, 2014

Generally speaking you do not need to close and open a new PR to update one that you have already submitted.

Just make your changes, use git commit --amend (to update the commit), then git push --force.

@dsawardekar
Copy link
Contributor Author

Thanks, I'll definitely keep this in mind for future PRs!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants