Calling Developers!
We are reenergizing our code contribution process! Learn More

What are the Slack Archives?

Itโ€™s a history of our time together in the Slack Community! Thereโ€™s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you wonโ€™t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

Is there any limitation that requires transfer.xml files to be named after the module's name? Some f

Options
UKHR9UN00
UKHR9UN00 Posts: 70 ๐Ÿง‘๐Ÿปโ€๐Ÿš€ - Cadet

Is there any limitation that requires transfer.xml files to be named after the module's name?
Some files grow very large and splitting could be useful. On the other hand I haven't seen this very often yet, and I wonder if that's for a reason. ๐Ÿ˜„

Comments

  • UKGT7RC7P
    UKGT7RC7P Posts: 538 ๐Ÿง‘๐Ÿปโ€๐Ÿš€ - Cadet
    Options

    don't think so, afaik it merges all *.transfer files regardless of name

  • UK5DS29L2
    UK5DS29L2 Posts: 546 ๐Ÿง‘๐Ÿปโ€๐Ÿš€ - Cadet
    Options

    I think this is just so it's easy for you to find out where they are used AND so they have unique name

  • UKGT7RC7P
    UKGT7RC7P Posts: 538 ๐Ÿง‘๐Ÿปโ€๐Ÿš€ - Cadet
    edited October 2019
    Options

    think they can all be named transfer.transfer.xml ?