On ember-cli config is stored in config/environment.js file and it can be
accessed at any time of app being booted. Till now we were using Travis.config
which was making things hard, because we needed an application instance to get
any config value. This commit moves config to config/environment.js and allows
to access it at any point of loading the app.
Our ajax function was passing params as object to xhr.send function.
For some reason this breaks on Firefox 34.0 beta. Sending stringified
version of params works correctly.
After upgrading ember to 1.8.1 tests pass, but I found a few cases where
things break (for example when navigating between certain routes). I'm
reverting for now.
This reverts commit fa5e9179af, reversing
changes made to 978c887123.
We have a bug that results in sending unneeded ajax queries on missing
log parts. I'm working on a fix, but it may take a while, because I want
to refactor a few parts of the app instead of putting more hacks on
legacy code. To help with the situation I'm increasing timeout for
pusher fallback.
* Add `travis.source_endpoint` meta (fixes many tests with hard
expectations on `http://github.com` being in URL paths).
* Wrap `Ember.run.once` in a `Ember.run` (prevents test auto-run
assertion).
* Fix expect counts for a couple tests.
When changing adapter to make it work with env vars I used PATCH method.
Hooks are using PUT to update active fields, so it broke hooks. This
commit moves saveRecord with PATCH to env vars' adapter.
For some cases (like coming env vars) we will need to also pass a
repository id to the URL, so I'm passing it from createRecord and other
methods which handle records.
arrayComputed was added recently in order to make array computations
easier. Using arrayComputed we can improve LimitedArray which now uses
an isolated multipurpose Ember.computed.limit.
I found the commit that caused the bug that caused me to do the last
revert. I'm therefore reverting the previous revert and I will be
committing a revert that reverts the commit that introduced the bug. See
next commit.
This reverts commit db2d38a7af.
It seems that directly setting location.hash directly doesn't play nice
with Ember.js URL handling - using it to handle line numbers results in
weird bugs (URL stops being updated after setting hash manually).
This commit gets back to using window.history.pushState() which was
changed to direct hash manipulation in ff1aad3
