fix: Fixed issue where a level component's iid component reference was assigned a previous layer#71
Conversation
|
@Cammin please check this! |
|
Ah interesting, thank you! I do want to investigate this a bit. |
|
Not necessarily the pull request title. The actual commit. This is something I've wanted to figure out for all my pull requests and haven't found out yet, it is partly why I haven't gotten to them soon enough 😅 |
|
Like, if there's a way I have control over that, etc. there probably is a way and I just need to look into it |
I just tried to figured out and changed the title.haha |
…s assigned a previous layer
|
Now it should be right! @Cammin |
|
Awesome! Thanks for the swift work, hopefully didn't burden you much, haha |
With pleasure. : ) |
|
I'm going to review it a bit before going ahead with it, I think there might be a way to grab a cached value instead of getcomponent. But if not, then I'll complete the request |
That's great! |
|
I made some changes here: 1054564 |
|
🎉 This PR is included in version 6.12.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Here should be level's iid but it had been iid of last layer.