We used to get ‘this is going to get deprecated’ notices in our log output for various Kepler-related classes/functions and this was expected earlier in the dev cycle for this new platform. But now I’m seeing a new one (for useComponentInstance():
(NOBRIDGE) WARN useComponentInstance is deprecated. Update to use getComponentInstance from KeplerAppStateManager instead. useComponentInstance will be removed in a future release
and this is from like very new code! Much of our integration or feature code is helped along by actual Amazon engineers who give us code examples using soon-to-be-deprecated patterns!?? I know fast changes are occurring but some heads-up would be nice. Not everyone watches log output!! Again; not all of our developers would notice this log output. I think it would be best to include such deprecations in the release notes or somewhere related to the release notes. Very very frustrating to see these so close to Kepler release. Again, trying to be patient with fast changes in the Kepler stuff but ya’ll are notorious for never having your docs match the experience (I’ve complained before and ya’ll have fixed→thank you for that but it is an ongoing problem). I feel like deprecations like this will bite us all in the rear end (had to make this G-rated). I’m concerned about future deprecations. Sorry; Saturday work makes me grumpy it seems. Please please announce deprecations here. We won’t always see the log output. That is just a fact of life it seems.