Skip to content
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

scope.$apply-async(resizer) #1

Merged
merged 1 commit into from
Apr 17, 2019
Merged

scope.$apply-async(resizer) #1

merged 1 commit into from
Apr 17, 2019

Conversation

dotKev
Copy link

@dotKev dotKev commented Apr 17, 2019

Suppress $scope.digest already in progress errors.

Changed scope.$apply(resizer) to scope.$apply-async(resizer)

This issue was tangentially related to patrickmarabeas#46 (comment).

@dotKev dotKev self-assigned this Apr 17, 2019
Copy link
Member

@jguthmiller jguthmiller left a comment

Choose a reason for hiding this comment

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

Any context as to why it needs $applyAsync? It would just be helpful to have in case it ever gets addressed upstream, especially if the upstream solution ends up being different.

Also, you shouldn't need to merge this PR in order to test it locally. Hit me up if you need any help with that.

@dotKev
Copy link
Author

dotKev commented Apr 17, 2019

I can test locally. Just wanting to reference the version number in mysidewalk/frontend.

@dotKev dotKev merged commit e6d58bb into master Apr 17, 2019
@jguthmiller
Copy link
Member

Is this a documented issue upstream? If so, should we submit a PR for it? If not, should we submit an issue? I only ask because this seems like an issue that other people might have already ran into.

@jguthmiller jguthmiller deleted the apply-async branch April 17, 2019 21:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants