The Welkin Suite Forum

Can't open a Lightning component unless all of the parts are there :-(



Can't open a Lightning component unless all of the parts are there :-(

  • Please log in to reply

#1
mac version welkinsuite

marc.behr

    Posted 18 Oct 2018 and edited 22 Oct 2018

    I am using Blaze R16 and working on a lightning component. My component only needs the component and controller, so I deleted the other files (css, document, svg, etc). Now I can't open the component in Welkin Suite... Do I really have to have all of the parts to be able to work on a component in WS? When I double click on any of the remaining files now that I ahve deleted the extra files, nothing happens.

    Is this a 'feature' (I hope not) or a bug?



    3 replies to this topic

    #2

    kate.dulko

      Posted 19 Oct 2018

      Hi Marc,


      Thank you for sharing this issue with us.


      First of all, may I please clarify with you which way did you delete Lightning files which you didn't use (css, document, svg, etc)?


      In general, since the IDE works with Lightning files using whole bundles, this is required to keep all the files from bundles in the IDE. An information about all the members of any Lightning bundle is present in a project file, and if any of these files is absent this can cause issues.


      Also, you can send us a bug report with attached log files, however, if the files are absent locally, this can be a reason for the issue.


      Thank you,

      Kate


      Kate Dulko
      Customer Relations

      The Welkin Suite

      twitter: @KateDulko
      skype id: d_katerina
      e-mail: kate.dulko@welkinsuite.com

       

        


      #3

      marc.behr

        Posted 19 Oct 2018

        Hi Kate,

        I deleted the files outside of WS (just did a rm from the command line) since WS would not alolw me to delete them. So based on your explanation, that sounds like it would be the issue. Since Salesforce does not require that we have all of the bundle files, why would WS?

        Marc



        #4

        kate.dulko

          Posted 22 Oct 2018

          Hi Marc,


          Thank you for your response.


          A reason for the issue is that the files which are included to a bundle are absent locally.

          TWS doesn't require to create all of the members inside a bundle, however, in the case when members are present in a bundle in your organization, the IDE needs to have them locally in your TWS project.

          This is a currently implemented mechanism: when you open any bundle in the editor, the IDE opens all included members and all of the other processes, like pull or deploy, are based on the work on a whole bundle. And the information about a bundle and its members is included in a project file.


          Also, I should note, that we consider changes for Lightning functionality, and probably in the future, we will implement a mechanism when you are able to work on each Lightning file separately. However, currently there are some dependencies between a bundle and its members and this is a core for the work on Lightning in the IDE. 
          We are looking for the best way to provide you with all the necessary and additionally useful features for the Lightning, and I will keep you updated on our progress on this. I believe we will start working on such changes during the nearest months.


          Regards,

          Kate


          Kate Dulko
          Customer Relations

          The Welkin Suite

          twitter: @KateDulko
          skype id: d_katerina
          e-mail: kate.dulko@welkinsuite.com

           

            





          Boost Your Productivity. Get Started Today

          Try Free Trial