The Welkin Suite Forum

Lightning Component Bundle API version files missing in version control source



Lightning Component Bundle API version files missing in version control source

  • Please log in to reply

#1
windows version welkinsuite

vchaddha

    Posted 15 Jul 2019 and edited 25 Jul 2019

    How do Welkin Suite manage Lightning Components Bundle API versions in projects ? I've found the metadata xml files are missing in source folders. I was using Github repository to save the source and I realized that all the lightning component folders are missing "-meta.xml" files and due to this when i deploy the code into any organization it is not recognizing the API bundle for that component and platform auto picks latest version in those cases and some components are breaking in deployment because versioned validation imposed by platform for certain features in the code to work. 

    Am I missing some kind of configuration in the IDE to fix this situation?


    PS - It's really hard to get Welkin Suite support's attention, even though the IDE is a paid subscription there is no way we could reach out to support directly it seems, I tried email contact as well but no response, I had the question opened in forums in different place and there wasn't any response there as well. I hope someonw checks this and let us know how to manage this situation.



    4 replies to this topic

    #2

    ihor.zhabolenko

      Posted 16 Jul 2019

      Hello Varun.


      We need to admit to you and our users that we totally fumbled the ball on supporting your questions that you emailed to us over the last week and wrote on the forum. On your case, we did not deliver the level of support that we hold ourselves to. You definitely should have had a response from us last week. We found the points that caused this to happen and took action to plug the holes around it.


      Thank you one more time for contacting us on this and for bringing this issue to our attention.
      I've added the appropriate ticket to our development backlog and we will work to solve the issue. We will release the fix for this issue as soon as possible. (hopefully next week)
       
      As a workaround, please create a new TWS project and the necessary *.cmp-meta.xml file will appear in this project.
       
       
      Best Regards,
      Ihor
       



      TWS Team


      #3

      ihor.zhabolenko

        Posted 25 Jul 2019

        Hi Varun,


        We've just published a new version with a fix for this problem. Please find more details about this release in our blog - release notes.

        Your TWS will update automatically very quickly.


        Please let us know if this issue is fixed for you.


        Regards,

        Ihor


        TWS Team


        #4

        vchaddha

          Posted 25 Jul 2019

          Hi Ihor,


          The update works as you expect it to be, looks good, thanks for that.


          Though I think the meta.xml files should be available in IDE as well. Does that mean it can't be edited from DIE, because at one stage I remember I was adviced not to change local project related files outside of IDE, as it could end up in unwanted errors. I think it would really help if XML files are part of IDE, just like all other components do including LWC. It's really easy to change API version from within DIE that way.



          #5

          ihor.zhabolenko

            Posted 25 Jul 2019

            Hello Varun.


            Thank you for your reply. 

            We like it and I've added your feature request (ability to change -meta.xml file from the IDE) to our development backlog. 

            However, right now I cannot tell you when exactly this will be implemented.


            If you have any other suggestions, please share them with us. We will be happy to hear your ideas.


            Regards,

            Ihor


            TWS Team





            Boost Your Productivity. Get Started Today

            Try Free Trial