Testing

Simply cd into each package and run tests with ember test or
ember test --server.

Known issues with this workflow:

At the time of writing, nested addons are not officially supported by Ember CLI.
In our case, they generally "just work", however anything that requires file
watching or linting on a nested package (like core or checkouts) will break.
You'll need to restart your server when changing core or checkouts.

Please see "Pull Requests" below for more information.

Questions

This is the issue tracker for spree-ember. The community uses this site
to collect and track bugs and discussions of new features. If you are
having difficulties using spree-ember, please search the issues, and if you
can't find anything useful, go ahead and open an issue. Someone will help you
shortly.

Issues

Think you've found a bug or have a new feature to suggest? Let us know!

Reporting a Bug

Update to the most recent master release if possible. We may have already
fixed your bug.

Search for similar issues. It's possible somebody has encountered this bug
already.

Provide a demo that specifically shows the problem. This demo should be fully
operational with the exception of the bug you want to demonstrate. The more
pared down, the better. Issues with demos are prioritized.

Your issue will be verified. The provided demo will be tested for
correctness. The team will work with you until your issue can be
verified.

Keep up to date with feedback from the team on your ticket. Your
ticket may be closed if it becomes stale.

If possible, submit a Pull Request with a failing test. Better yet, take
a stab at fixing the bug yourself if you can!

The more information you provide, the easier it is for us to validate that
there is a bug and the faster we'll be able to take action.

Requesting a Feature

Search Issues for similar feature requests. It's possible somebody has
already asked for this feature or provided a pull request that we're still
discussing.

Provide a clear and detailed explanation of the feature you want and why it's
important to add. Keep in mind that we want features that will be useful to
the majority of our users and not just a small subset. If you're just
targeting a minority of users, consider writing an addon library for
ember-cli.

If the feature is complex, consider writing some initial documentation for
it. If we do end up accepting the feature it will need to be documented and
this will also help us to understand it better ourselves.

Attempt a Pull Request. If you are willing to help the project out, you can
submit a Pull Request. We always have more work to do than time to do it. If
you can write some code then that will speed the process along.

Pull Requests

We love pull requests. Here's a quick guide:

Fork the repo.

Ensure you have the development requirements:

node (0.12 recommended) or io.js (1.x) -- do not install node using sudo

npm (2.x)

phantomjs

Run bootstrap.rb to ensure each addon is working against itself.

Run bootstrap.rb from the spree-ember root of the project. This will set
the Addons to run against each other, ensuring that changes you make across
multiple packages work with each other.

Add a test for your change. Only refactoring and documentation changes
require no new tests. If you are adding functionality or fixing a bug, we
need a test!