The Welkin Suite Forum

[Implemented] Store project structure in custom metadata



Store project structure in custom metadata

  • Please log in to reply

#1

tim

    Posted 18 Nov 2015

    I'm interested in keeping my project's classes, triggers, etc. in custom folders, but I cannot, since this data is currently stored in the .sfproj file.  This is OK if the team is using a version control system (VCS), but even in that case it can still problematic for two reasons:

    1. Login credentials are also stored in the .sfproj file, preventing me from committing it to (VCS)
    2. If I create a NEW project within Welkin Suite, the folder structure is not preserved - I have to build it again any time I create a new project.

     

    The two above problems make custom project structure useless to me as a developer because I work on a team, and we do not currently use a versioning system (I'm fighting that battle right now, but currently that's the way it is).  This is unfortunate, because custom project structure is an AWESOME feature!

     

    I propose that TWS start storing custom project structure data in a custom metadata type (see here).  Custom metadata type records are themselves stored as metadata, making it ideal for this use-case.  E.g. a custom metadata type could include a field for file-path, file-type, and last-modified time (last modified of the custom path, not of the file itself).  Welkin Suite could then retrieve and update these custom object type records as part of its regular push/pull action.  Any files which do not have an entry in the custom metadata type would be placed in Welkin Suite's default locations.

     



    2 replies to this topic

    #2

    vlgubanovich

      Posted 23 Nov 2015

      Hi Tim,


      Thank you for such a detailed suggestion on how to improve customizable project structure!

      The good news is that we are going to resolve all the issues mentioned by you pretty soon - we aim to get this done before 2016.


      And our ideas are very close to what you suggest:

      • Remove credentials from the project file, so you will be able to share it using Git or any other version control system while credentials would be stored elsewhere and ignored by Git
      • Start using Custom Metadata (or anything else in the org itself, if Custom Metadata won't fit our needs) to store information about the project structure in The Welkin Suite
      • Provide a switch in options which will instruct TWS to modify project structure without changing files location in the file system itself so you will be able to work with projects that were created and developed in other IDE's at the same time

      I will keep you updated on our progress with this changes.


      Thanks,

      Vladimir


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


      #3

      kate.dulko

        Posted 02 Mar 2017

        Hi Tim,


        I hope you are doing well.

        I want to inform you that your current feature request is implemented in The Welkin Suite IDE as the 'Project Structure Sync' option. This was added in the Beta 0.26.7 version of The Welkin Suite. 

        You can use for new TWS projects or for your existing ones.


        If you have any additional questions, please write us. We will be happy to answer them.


        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