-
Notifications
You must be signed in to change notification settings - Fork 119
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
Strike Select - doneRendering needs to check for v.value is present #92
Comments
It appears we need to use the doneRendering event to handle the addition of options through a callback. In this case we need to also make sure that the doneRender checks to see if there is a v.value as well as a v.valueLabel otherwise when a component gets destroyed its stuck in an infinite loop due to not having a label, but theres no value to set a label. |
expect this to be resolved in our next release, added the check for v.value. |
@chewy2 I think I ran into this issue today with version 0.9.0 of the select component. I started receiving the error below in certain circumstances. Is this the same thing? Here's the specific offending code/function in file strike_selectHelper; more specifically this line component.get('v.body').forEach(function(child) {
The function above is eventually called, but the top of the stack trace is this function in the same file:
Which calls this function
The line var options = helper.getChildOptions(component, event, helper); calls the first function I included above. Any help, or insight would be much appreciated. Thanks in advance! |
The doneRendering code needs to be moved to an afterRender in the renderer. The doneRender code only needs to be ran once, but its currently running infinite times and causing infinite loops under certain conditions.
The text was updated successfully, but these errors were encountered: