We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Please explain the suggested feature in detail.
At the moment order is:
value1 will be set value1 hook will be called value2 will be set value2 hook will be called
for initial state (when objects spawns) it seems like it would make more sense if all the hooks are called after all values are set
value1 will be set value2 will be set value1 hook will be called value2 hook will be called
The text was updated successfully, but these errors were encountered:
Maybe not only for initial state. For every state
Sorry, something went wrong.
refactor: setting all syncvars before calling hooks for initial spawn
b678da7
resolves: #913
00b7e3a
refactor: setting all syncvars before calling hooks for initial spawn (…
7d4cd20
…#915) * refactor: setting all syncvars before calling hooks for initial spawn resolves: #913 * implementing code
🎉 This issue has been resolved in version 105.1.0 🎉
The release is available on GitHub release
Your semantic-release bot 📦🚀
Successfully merging a pull request may close this issue.
Please explain the suggested feature in detail.
At the moment order is:
for initial state (when objects spawns) it seems like it would make more sense if all the hooks are called after all values are set
The text was updated successfully, but these errors were encountered: