-
Notifications
You must be signed in to change notification settings - Fork 21
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
new installation problem #67
Comments
Looking at this, it seems like changes from 0.0.4 vs master. I'm guessing Aurelia, being pre-beta, is evolving faster than developers can release updates to address breaking API changes. The quick fix for this particular problem is, in
replace the Do the same in This may or may not solve your problem. I'm getting a different error now that doesn't reference aurelia-bs-grid, but that goes away when I remove the
I also note that when I install with jspm, |
Followup: Using Skeleton 0.19.0 instead of 0.20.0 looks like it will solve the problems, maybe. I'm down to an issue with aurelia-http-client:
It is pulling newer versions of a couple of Aurelia packages, so I'm guessing it needs to be forced to a newer version too. Or maybe swapped out for the fetch client. Hopefully, I'll get this working today. NOTE: all the samples except remote data work fine. After, I may try to beat together a 0.20.0 compatible branch, but want to see the unmodified code working first so I know what the issues are. Although, given official beta's impending release (according to the latest on the Aurelia blog), it may be wiser to wait until that's settled. |
thanks for help, i have try with master but still not working ... |
After further research, aurelia-templating 0.17.0 removes Then I discovered that bindingEngine is now BindingEngine, set up to inject it, but the grids in the sample all come up blank, so I'm guessing I'm doing something wrong and don't understand what's going on well enough to untangle it. @charlespockert: If it helps get this plugin functioning with current versions of Aurelia, you can see my work on the plugin so far at: https://github.com/jmjf/aurelia-bs-grid/tree/skeleton-0.20.0. I've also pushed the repo I've been using to test at https://github.com/jmjf/skel-0.20.0--which is navigation-skeleton 0.20.0 with the aurelia-bs-grid sample app copied to src, aurelia-http-client 0.13.0, and aurelia-bs-grid from my repo's skeleton-0.20.0 branch. @denimaaark: Until this repo is updated, you can clone the navigation-skeleton repo, checkout 0.19.0, |
The skeleton-0.20.0 branch of https://github.com/jmjf/aurelia-bs-grid/tree/skeleton-0.20.0 is fixed for skeleton 0.20.0, I think. After updating the dependencies, there were three breaking API changes between skeleton 0.19.0 and 0.20.0. I fixed the bindingEngine -> BindingEngine change noted above by injecting BindingEngine and assigning it to this.bindingEngine and replacing the one use of bindingEngine with this.bindingEngine. I fixed the viewSlot.swap() removal by copying the code from skeleton 0.19.0 and making minor adjustments to fit the context. The major issue turned out to be a change in the API for ViewFactory.create(). In the previous release, it accepted a bindingContext parameter. In the current release, bindingContext must be set after the view is created with view.bind(bindingContext). That is why nothing displayed in the grid container in the previous note. It works for all examples, I think. See Pull #69 and the repo branch noted above for details. Scary thing is, I think I'm staring to understand Babelified ES5. |
I always look at the ES5 and not the pre-transpiled code :) - you get used to it Thanks for the work so far! |
Charles, very nice grid. Sadly it doesn't work on Aurelia 1.0.1 with installation issues |
Hello, i have installed new versions of aurelia and grid.
I have errors when included plugin aurelia-bs-grid
Unhandled promise rejection Error: (0 , _aureliaFramework.skipContentProcessing) is not a function(…)(anonymous function) @ es6.promise.js:138
es6.promise.js:138 Unhandled promise rejection Error: (0 , _aureliaFramework.skipContentProcessing) is not a function(…)(anonymous function) @ es6.promise.js:138
es6.promise.js:138 Unhandled promise rejection Error: (0 , _aureliaFramework.skipContentProcessing) is not a function(…)
The text was updated successfully, but these errors were encountered: