Twan Duvigneau: No the final release will not contain import/export of fieldmapping. This is something we will add later on probably with the import target connector from Github.

Rick van den Dijssel: will the target system import work the same way as the source import? Because with targets especially it would be nice not to have to select something from a GitHub repo when you build something yourself

Twan Duvigneau: Do you mean you want the old option where you can select a default/simple script option? Because we have this in source the default option that we had before is now selectable in github as "source template" and is always on top of the source system list. We want to support the same features for importing in the target system (offcourse not planned yet). Another advanced is that we can supply multiple templates like a template for csv, SQL or rest api as example which helps you when setting up a system from scratch. Hopefully this answers your question.

Rick van den Dijssel: We'd rather have the old one, because the "source template" loads in the readme from the github and links to it. Which is not connected to the system at all. This is a bit confusing and quite ugly. It also does not add anything that I know the system is based on Source Template V1.0.4 for example, because its only a template that will be heavily changed/filled with other code.

Templates for CSV/SQL/API/Generic are nice to select during import, but I dont want the link to the github repo. If the readme/connector is based on x would not be imported for the template targets/sources then that would be way better in our opinion. Or perhaps make the link to the github repo and readme configurable, it does not have to load in the code, as long as it can do the readme and link.