The Welkin Suite Forum

Automatically add/remove files to/from project



Automatically add/remove files to/from project

  • Please log in to reply

#1

victor.paskel

    Posted 06 Jul 2016 and edited 07 Feb 2018

    Hello guys.
     

    It would be nice if you could do automatic project update(maybe an option in project context menu) if there are changes in local file system.


    e.g.:

    1. When I recreate project I want to add my previous soql and anonymus code files to project just by moving them to \AnonymousApex and \Soql folders.
    2. When *.cls file is created in folder add it to project. And when file is missing in folder remove it from project or maybe even try to remove it from Salesforce.

    Thanks


    • 1

    7 replies to this topic

    #2

    kate.dulko

      Posted 07 Jul 2016

      Hi Victor,


      Thank you for your suggestions.

      I've added both of them to our Backlog.


      I'll contact you when this will be available in The Welkin Suite, but I cannot tell exactly when.


      Regards,

      Kate


      Kate Dulko
      Customer Relations

      The Welkin Suite

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

       

        


      #3

      john.harcourt

        Posted 12 Jul 2016

        Visual Studio currently supports the "Add => Existing Item..." and I was hoping this would be available in TWS.

        I've had the same need that the above user brought up.  This would be a nice addition.  Having the ability to save Anonymous Apex and SOQL statements is a great thing and I've shared these files with other developers, but we need this ability to easily add these files to our projects.


        Thanks!


        • 1

        #4

        kate.dulko

          Posted 13 Jul 2016

          Hi John,


          Thank you for your comment.


          We understand that adding of existing items is the useful option, and our developers are going to implement this in one of the nearest versions of The Welkin Suite.


          I'll keep you updated when this will be available inside the IDE.


          Regards,

          Kate


          Kate Dulko
          Customer Relations

          The Welkin Suite

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

           

            


          #5

          dhetesi

            Posted 23 Jan 2018

            How is this still not a feature after a year and a half? We have multiple developers working in independent dev environments sharing codet through Git. If a new class is pulled down through Git there's no way to add the file to project. If a file is pulled before adding the file to Welkin, then file has to be deleted, a blank file is added to Welkin, then file is pulled again. 


            • 1

            #6

            vlgubanovich

              Posted 29 Jan 2018

              Hi dhetesi,

              I completely understand your critics and appreciate your feedback!

              The reason why this functionality is not yet implemented - the regular Salesforce project in TWS is tied up directly with the organization, thus a lot of additional information is stored from a Salesforce organizaiton. For example - hashsum and "remote" modification date for all items. In this way we can ensure that you get the smooth experience with builds/pulls.

              At the same time having SalesforceDX there's a great alternative to the old approach - SFDX allows really smooth teamwork, but yes, it requires some initial investment of time to migrate.

              We are now looking for different ways how we can make life easier for those who use Git without SFDX - once we'll finalize a good user-friendly approach that won't require huge changes in TWS codebase and logic we'll definately include it into our sprint asap.

              Thank you,

              Vladimir


              Vladimir Gubanovich
              Head of Product
               
              The Welkin Suite
              skype id: vladimir.gubanovich
              e-mail: vladimir.gubanovich@welkinsuite.com


              #7

              bvanburen

                Posted 02 Feb 2018

                Its unrealistic to expect all organizations to adopt DX.  If the company or client does not use DX and hands you a sandbox you cant use DX.   

                The only way around this it to open the project in the eclipse app and move you stuff around 




                #8

                vlgubanovich

                  Posted 07 Feb 2018

                  Hi Bruce,


                  You've pointed to an interesting topic - usage models. To be honest I've rarely seen cases when a client provided a sandbox for a long-running project where I'd need to allocate a team of developers and use Git. In case if it's not a long-running project, or if there's no "team" that works on a project - I'm not sure that I see and understand the exact flow that you apply and how you'd use the discussed feature in your flow. I'd really appreciate if you can shed some light on it so we'll understand the case better and will keep it in mind, when we'll get to the question of additional metadatas/adding existing files/unlinking projects from orgs.

                  At the same time there's a good option (for long-running projects, of course), to use own DevHub to spin-up scratch orgs for clients projects development and testing. But, of course, it's also not always possible and won't work for every case.


                  Regarding workarounds - I've posted another workaround, that involves Ant migration tool, here on the forum. Pull from Git -> deploy with ant task -> Open TWS project -> Pull from your organization -> develop -> push to the org -> retrieve with ant task -> commit & push to Git. I know that it's a workaround and not a completely straightforward way, but there's no straightforward way (without a lot of caveats) to work nicely with Git and regular SF projects. It might look as a complex workaround, but in terms of time required to "prepare" and "execute" it - looks not very bad (i.e. 30 minutes to prepare 2 ant tasks for your specific needs with package.xml + 1-3 minutes on every pull/push to execute Ant).


                  Finally, we already have some interesting ideas how to resolve a bunch of cases at once - as I've mentioned above it's "additional metadatas/adding existing files/unlinking projects from orgs". As such solution will be a significant update to a concept of a project, as it will also require changes to the build & pull processes and as a migration for existing projects will be needed - we're analyzing it carefuly right now and trying to find any gaps in the logic and in the nice flow that we've built for most of the cases. If all will be good on the stage of detailed analysis - we'll do our best to implement this soultion as soon as we can.


                  Hope this answers.


                  Thank you,

                  Vladimir


                  Vladimir Gubanovich
                  Head of Product
                   
                  The Welkin Suite
                  skype id: vladimir.gubanovich
                  e-mail: vladimir.gubanovich@welkinsuite.com





                  Boost Your Productivity. Get Started Today

                  Try Free Trial