You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The size will unexpectedly evaluate to zero. If you in any way inspect w.child_generic_works then the size gets updated to what it should be. The "&& nil" is there just so the console doesn't automatically inspect it when testing this in console. In actual code that would not be needed to reproduce the bug.
This doesn't seem to be a Hydra-works specific issue though. You can replace the class with this and the bug is still present
I came across this issue while trying to do something like this with Hydra-works.
The size will unexpectedly evaluate to zero. If you in any way inspect w.child_generic_works then the size gets updated to what it should be. The "&& nil" is there just so the console doesn't automatically inspect it when testing this in console. In actual code that would not be needed to reproduce the bug.
This doesn't seem to be a Hydra-works specific issue though. You can replace the class with this and the bug is still present
The bug also happens if you push the new work to w.members instead of w.child_generic_works. w.members.size however always gives the expected value.
The text was updated successfully, but these errors were encountered: