Skip to main content
Archived

Option to split up workspace file to make working with gitflow easier

  • August 10, 2021
  • 0 replies
  • 11 views

itsmatt
Celebrity
Forum|alt.badge.img+47

When working with git and FME together it's pretty difficult to perform code review and to merge changes, at least if the same .fmw file is touched.


What would really help is the ability to split up an .fmw into a number of files so that changes and merge conflicts can (more) easily be resolved.


For example, one file could be just list the transformers and parameters set, one file to handle the content of comments and bookmarks etc, and one project file which has the positions and workspace parameters etc.


If a developer could use a structure like this changes would be much clearer and it would be much easier to compare git-branches.


Opening the project file would be the same as opening up a workspace, the files would be compiled together.


There would also need to be a way to compile the files into a normal .fmw file so you could include this step in a build pipeline.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.