Calling Developers!
We are reenergizing our code contribution process! Learn More

What are the Slack Archives?

It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

Hello o/, I just came across something that kind of confuses me. the current documentation (of featu

U01FKQ0S909 Posts: 20 🧑🏻‍🚀 - Cadet

Hello o/,
I just came across something that kind of confuses me.
the current documentation (of feature 202009.0) about frontend components is saying: quote:

It is recommended to use ready callback.

and the corresponding code is saying:

     * Same as mountCallback().
     * @deprecated Use init() instead.
    protected abstract readyCallback(): void;

and this source was last changed almost 2 years ago. so i did a little bit of research on
the deprecation is in the spryker-feature/spryker-core sind version 201903.0 .
well.. now i am having a few questions:
• 4 spryker-core versions later how long is it going to be deprecated?
• when will it be removed and switched to the recommended function?
• (why is the documentation recommending a deprecation? I guess nobody noticed. can this be updated?)


  • Aleksander Kovalenko
    Aleksander Kovalenko Sprykee Posts: 45 🧑🏻‍🚀 - Cadet

    Hi Tien. Thanks a lot for pointing out our issues in documentation, we gonna update this article soon. According to your question when deprecated method will be removed - whenever we have a Major release for ShopUi module, as long as we cann’t change API in a Minor - For now ShopUi Major release is planned for the 3rd quarter of 2021.