Skip to content

Angular 1.6 "Possibly unhandled rejection: canceled" fix. bug number #5890 #5949

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

Merged
merged 24 commits into from
Feb 27, 2017
Merged

Angular 1.6 "Possibly unhandled rejection: canceled" fix. bug number #5890 #5949

merged 24 commits into from
Feb 27, 2017

Conversation

dominusbelial
Copy link
Contributor

using sebastian-zarzycki-es solution i have added ".catch(angular.noop)" to all the offending promises on the latest 4.0.2 uigrid for angular 1.6.1

@mportuga
Copy link
Member

What is the bug number?

rowHeader.colDef.visible = newVisibility;
grid.queueGridRefresh();
if ( rowHeader ) {
if ( rowHeader.visible !== newVisibility ) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not do a single if statement?

if ( rowHeader  && rowHeader.visible !== newVisibility ) {

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bug #5890

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i will update to single if statement

@dominusbelial dominusbelial changed the title Angular 1.6 "Possibly unhandled rejection: canceled" fix. Angular 1.6 "Possibly unhandled rejection: canceled" fix. bug number #5890 Jan 23, 2017
@goleafs
Copy link

goleafs commented Feb 1, 2017

is this pull request going to be accepted? would obviously prefer to stay on the main code base!

@mattbrunetti
Copy link

@goleafs Are you using this branch? If you've tested this let us know and it's more likely to be merged

@goleafs
Copy link

goleafs commented Feb 7, 2017

I made the same changes locally, have used it for a few days with no issues.

@mportuga
Copy link
Member

mportuga commented Feb 7, 2017

@goleafs We will merge this. Unfortunately, we are currently busy with our day jobs right now, so we had to stop working on Ui-grid for a bit. We also are having a weird issue with the travis build. Once the travis build issue is resolved, we will see if we can get around to all of the open PRs. I am sorry for the inconvenience.

@Oceanswave
Copy link

+1

1 similar comment
@ivorobkalo
Copy link

+1

@Nickproger
Copy link
Contributor

Really waiting for it... :) This is the last think that block us to switch to Angular1.6...

@aamcatamney
Copy link

+1

1 similar comment
@NageshTembhurnikar
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants