MergeTagger doesn't respect field order (in contrast to v. 2.x)

[bes-shutok]

Hey! Thank you for your work on the project.

We are currently moving from 2.x to 3.x version. In this process I found that MergeTagger doesn't keep the provided order of the fields it merges. In reality the fields are merged in the order of appearance in metadata (Property object).

For example

                <merge toField="asset.name.tds" singleValue="true" singleValueSeparator=" - ">
                    <fieldMatcher method="csv">name,name.tds</fieldMatcher>
                </merge>

can now resolves either in ${name} - ${name.tds} or in ${name.tds} - ${name}

Is there any plans /possibilities to fix that in the future? Do you accept external pull requests?

Best regards, Andrey

[ohtwadi]

Hi Andrey,

We very much appreciate external pull requests :)