-
Notifications
You must be signed in to change notification settings - Fork 87
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
Allow execution on fastboot #110
Conversation
58c2b34
to
88941c7
Compare
@cesarizu My only question / concern is related to having "dummy no-op" implementation of But - I guess as long as our addon and components do checks to see if |
@dbouwman You are right. I've changed it to use |
👍 |
@miguelcobain Any chance we can get this merged? |
There are some things here that I don't understand. Why are we mocking |
For all "simple" methods there's the |
@cesarizu ah, ok. Makes sense. Thanks. Looks like Since all As a bonus, existing ember-leaflet plugins would also get fastboot support, as long as they only use Helpers would need to be no-op'ped if on fastboot, though. |
The initializer |
fa09f5e
to
839ee78
Compare
@miguelcobain I've updated this PR to use a About the initializer, with this code it doesn't need to be changed. Do you think that this still needs the |
Also about addons, I've been using |
@cesarizu We can't rely on proxies for this behaviour. I've outlined what I think a good strategy could be in this comment: #110 (comment) Do you see any problems with that rationale? |
Node.js supports proxies since version 6.0. This code would only run on fastboot, and fastboot requires node.js 4.2. I've updated the PR so that it works for version < 6 when using My approach was to make the use of |
I am in the process of updating my website so it can work with fastboot. I tried the @cesarizu:fastboot branch and I just wanted to report that it worked well for me after I moved to Node.js 6. All I had to do was to import the L module. Good job ! Can we expect this to be merged soon ? |
Closed in favor of #125 |
This PR is related to #74 and #104 but tries to solve the problem from a different perpective:
Currently, this allows my test app to run under fastboot with no errors.