-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Can no longer use a string for the gridOptions.data property #6155
Comments
I am facing the same issue with updating from 4.0.2 to latest version, any workaround for this? |
instead of using string in gridOptions.data, i am setting this value using service response. thanks for your clarification. |
I had the same problem and I've replaced the string binding with an empty array that was getting updated whenever I had the data ready. |
I've just run into this exact issue, first of all I believe that #6185 is a duplicate of this issue. The problem was introduced here in v4.0.3 - where that fastWatch check was present previously it meant the newData value was provided by the scope watch instead of that block of code at the top of the function. This means that where previously the value would be extracted from scope directly it is now explicitly extracted from appScope with the following implications:
I'd also like to note that the fastWatch option that features quite prominently in this area of the code doesn't appear to be documented anywhere. |
Same issue. downgraded to 4.0.2 |
@mportuga Thoughts? |
@mportuga this was caused by 75f98c3#diff-d586707ee1c4e842337e09afc6ebd587L87 We should be probably just restore the |
As of 4.0.3, I can no longer set the value of the gridOptions.data property as a string. For 4.0.2, it works perfectly, but in 4.0.3+, the grid is not rendered.
Here is a plunker that shows the issue: http://plnkr.co/edit/J9Xr3AuxI28FfxtYQstG
I'm not sure, but I believe the problem is inside the dataWatchFunction, because the newData array becomes undefined here.
The text was updated successfully, but these errors were encountered: