You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 3, 2019. It is now read-only.
Currently Build.xill generates one Mapper.xill robot that includes all mappings in a project. After solving #1, this should also be fixed. Expected behaviour would be to generate a separate Mapper.xill for config/import/ and config/export/ or a similar structure if you use multiple connectors for import or export. This is important, because it is more than likely that several connectors or import/export have overlapping naming for mappings and therefore need separate mapper robots. Also, while it may seem to make the project more complex by adding more separate files, it indeed makes the separate Mapper.xill robots more readable, because they only ever contain mappings for one system and one mapping.
Implement the expected behaviour by generating a separate mapper for each subfolder of config/ that contains a mapping/ directory. The resulting Mapper.xill MUST be stored in the subfolder, such that it may be included using for example include config.import.Mapper or include config.spimport.Mapper. Document the intended usage in a README.md.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently
Build.xill
generates oneMapper.xill
robot that includes all mappings in a project. After solving #1, this should also be fixed. Expected behaviour would be to generate a separateMapper.xill
forconfig/import/
andconfig/export/
or a similar structure if you use multiple connectors for import or export. This is important, because it is more than likely that several connectors or import/export have overlapping naming for mappings and therefore need separate mapper robots. Also, while it may seem to make the project more complex by adding more separate files, it indeed makes the separateMapper.xill
robots more readable, because they only ever contain mappings for one system and one mapping.Implement the expected behaviour by generating a separate mapper for each subfolder of
config/
that contains amapping/
directory. The resultingMapper.xill
MUST be stored in the subfolder, such that it may be included using for exampleinclude config.import.Mapper
orinclude config.spimport.Mapper
. Document the intended usage in aREADME.md
.The text was updated successfully, but these errors were encountered: