-
-
Notifications
You must be signed in to change notification settings - Fork 120
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
Angular 7 compatibility #36
Comments
The RxJS dependency is in If I look at one of your error with Export Service on this [line] it's imported this way import { Subject } from 'rxjs/Subject'; did that change in version 6? I need to support both RxJS 5 and 6 |
I see they changed their Observable, Subject etc. import { Observable } from 'rxjs/Observable';`
import { Subject } from 'rxjs/Subject'; becomes import { Observable, Subject } from 'rxjs'; I moved the RxJS 5 into the I am also finished refactoring for the new Major Release, can you please reply me on this RxJS ASAP since I'm already doing a Major (breaking) release. Also make sure to follow the Migration Guide, the new version changed quite a lot to support multiple grids |
Unfortunately, the support of C/C++ like macros is not yet supported in type script: microsoft/TypeScript#4892 |
This is an offcial migration document https://github.com/ReactiveX/rxjs/blob/master/docs_app/content/guide/v6/migration.md . It accentuates on the necessity of refactoring source code after a step of compatibility. |
So did you get it working without warnings? or are you saying that there's something to modify in my lib? |
With the use of rxjs@6 and rxjs-compat@6 , the waring disapeared. |
That's good news, I don't expect to support Angular 6 yet. Maybe in over a month but not now and I would not want to create 2 major versions just because of RxJS compatibility. Thanks for this info, I will leave the issue open in case someone else has the problem |
You Are Welcome 👍 |
Here's an attempt at the basic grid in Angular6 with rxjs-compat The grid looks exactly like what I got when I tried building it from angular.cli Any ideas? |
@ctung |
Thanks, that fixed it! |
@ctung |
Just so everyone knows, since there is a known way to bypass this issue. There are a few reasons
So will all these reasons, don't expect any resolution any time soon. |
When we expect angular 6 support? We are in Angular-5 and decided to migrate Angular-6. Only bottle neck slickly grid for angular-6 migrate. So please provide the angular-6 supported version for us at earliest. We are planing to go live at the month of Aug'2018 end |
@senthil1690 Please remember this is an Open Source and free project, if you want to contribute that would be awesome, else just wait as I am only 1 developer mainly on this lib and I have much other bigger priorities. |
@sabeurch @senthil1690 @ctung and everybody else... Things worth to know
You can install the RC version via (it's under a For a sample of the upgrade changes in your App, you can take a look at the Note that I will keep the Bootstrap 3 demo on version FEEDBACK are welcome I would like to have feedback if possible before tomorrow since I'm going on holiday starting tomorrow and I would like to make the version as official on NPM (it's under a Some Wiki might need updates, I'll do that later. For now simply look at the Bootstrap 4 GitHub demo (you can look at the |
Hey guys, I found a small problem with the date picker (Flatpickr) this morning, which I've now fixed. The problem was only showing in a production build and as I said it is now fixed. I had no news but I decided to make it official, |
@ghiscoding This is a good news , thank you so much for this good job 👌 |
Thank you |
@senthil1690 |
Actually the Angular Slick grid is not compatible Angular 6, errors of kind :
To by pass this issue, I downgraded the RXJS version from 6.0.0 to 5.6.0-forward-compat.5
This is a temporary solution, all errors related to angular slick grid disapeared, but when starting the application, this alert is displayed (in red):
Should this be worrying ?
The text was updated successfully, but these errors were encountered: