Closed vitaly-t closed 6 years ago
Following this logic, I should rename the global onInit
into onReady
also, because inside the app's onInit
we are in fact ready to do anything, so it is in fact the onReady
state.
This is going to happen for the official 1.0.0 release.
Therefore, re-opening the issue.
I am contemplating one breaking change, before this library hits version 1.0.0 - to rename
onPostInit
intoonReady
, to make it shorter, and with more accurate/precise meaning.If you think this is a good change - please vote, and/or leave your comments below!