Whitelist origin & Ng waitForApi fix#19
Conversation
…n in digest cycles This simplifies a lot of code
…ise will cause it to fail immediately. This allows it to fail gracefully in a Promise-like manner, in order for developer to handle rejection in their own particular way
|
No problem with adding tests, but how do you run them? |
|
After you run bower install
npm installyou should run grunt serveThis will run a local server on port 9000 and will run the unit tests on each file save. |
|
I've pushed some fixes based on your comments. I'm having trouble running specs, right now it's output is: |
|
What's odd is that init works fine when I'm testing on staging env. |
|
if you run grunt serve --forcethen you can debug the test if you open the browser on this page: localhost:8880/debug.html I'll try to take a look and see what does this test fails |
For example, if LS is disabled by browser
|
How come this never got merged in? The allowed origin functionality would be really nice to have. |
|
Because I didn't have specs for it. I no longer have time to write specs, can someone please take over it? I agree, I think the changes are rather important since origin whitelisting is a best practice for xd communication. |
|
it has a branch conflict. once it's resolved I'll merge it in |
|
@ofirdagan would you be okay to merge without specs if the conflicts were resolved? |
|
yup |
Fixes #18
Fixes #17