-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
attrs not updating correctly for contextual components #12613
Comments
Haven't dug into exactly what is happening just yet, but this is definitely a bug. |
While working on #12617 I'm also taking a look at this since both seem to touch the same classes. I have notice that |
I think I know what is happening. I'll check tonight (your this morning) |
Submitted a PR fixing this. The shortcat for rerendering was being done to soon preventing the arguments from the closure component to be passed to |
Rerendering a dot-syntax closure component failed to update the attributes due to the shortcut being done too soon. Fix emberjs#12613
@Serabe Thanks for your work on the fix. Would you be able to look at the updated twiddle. I've tried to clarify what I am expecting the behaviour to actually be (see the console). Essentially, I think that |
Reopening for review. |
I think when Ember Twiddle updates with the fix it should be ok. @rwjblue do you know if there is a way to test a twiddle with current master? |
https://ember-twiddle.com/5a29d14617527134ecad?numColumns=1 seems to be working properly (and using the correct SHA of Ember canary). @amk221 - Can you confirm? |
Confirm, it's working. Thanks! |
The RFC suggests I should be able to send along additional attributes to contextual components. If you add |
Please, can you send the updated tweedle? I did this and seems to work. |
@Serabe Yup, that's what I did too. Notice the difference in the console when you add that extra attribute? myProp does not increment, but it should? |
I see now. Proper support for glimmer components are still in the making. I'll take this into account. Thank you. |
Ok thanks, this blocks a feature I need to create a select box component - is there a place I can track this issue? |
Please see the console on this twiddle
Edit: Sorry, badly named issue. Not sure what the actual problem is just yet.
The text was updated successfully, but these errors were encountered: