Core component scenario question | Community
Skip to main content
jaibalaji
jaibalaji
New Participant
April 26, 2022
Solved

Core component scenario question

  • April 26, 2022
  • 3 replies
  • 1048 views

Hello all,

Recently I've come across this scenario when it comes to core components - Let's say we have developed a proxy component with v3 version as the supertype of Text component. This component has been dragged and dropped in hundreds of pages. We need to update the component to v4 after Adobe releases this v4 version. How do we update it without affecting the look and feeling of existing pages and not break anything? How do we give the author the power to choose the version on the page itself without developer changing the code? Basically the author should be able to change it on the page without developers having to change it through crx/de and push a code change.

Does anyone have ideas over this?

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Ravi_Pampana

Hi,

 

In your proxy you are referring to v3 core component, changing that to v4 should update in all the pages your proxy component is referred and pointing to v4. 

 

In order to give authors to select the version, it is good to create a legacy component referring to v3 core component and inform the authors to use that component, in case if they want to use older version of core component. 

3 replies

VeenaVikraman
VeenaVikraman
New Participant
April 27, 2022

Agree with @ravi_pampana  and @anish-sinha . Also in my opinion giving authors the flexibility to choose the text component version like you mentioned, is not a good idea( Even though it sounds fancy 😉). If there is an upgrade, let it go through proper code change ( in your case, your proxy component should now point to the new version rather than old one) . If they want to use both versions, you might have to create another proxy pointing to old version. 

    Anish-Sinha
    Anish-Sinha
    Employee
    April 27, 2022

    Hi @jaibalaji ,

    To summarize, there is no way authors can use the new version of the core components without any intervention from developers. As explained by Ravi, you can create a legacy component and keep both legacy and new version available for the authors. But there has to be new component created and checked in by the developers. The authors wont be able to do this by themselves without code change.

      Ravi_Pampana
      Ravi_PampanaAccepted solution
      New Participant
      April 26, 2022

      Hi,

       

      In your proxy you are referring to v3 core component, changing that to v4 should update in all the pages your proxy component is referred and pointing to v4. 

       

      In order to give authors to select the version, it is good to create a legacy component referring to v3 core component and inform the authors to use that component, in case if they want to use older version of core component. 

        Terms & ConditionsAccessibility statement

        Loading footer...