Skip to content

Conversation

@zerebubuth
Copy link
Member

Previous behaviour was to de-duplicate name variants with the same value as the main name tag. However, that breaks name fall-back logic when one doesn't want to fall back to the main name. For example, something tagged with name=Foo, name:A=Foo, name:B=Bar would remove the name:A tag, meaning that if the name preference display was A then B then local, it would display Bar instead of Foo.

Connects to #1406.

Previous behaviour was to de-duplicate name variants with the same value as the main name tag. However, that breaks name fall-back logic when one doesn't want to fall back to the main name. For example, something tagged with `name=Foo, name:A=Foo, name:B=Bar` would remove the `name:A` tag, meaning that if the name preference display was `A` then `B` then local, it would display `Bar` instead of `Foo`.
Copy link
Member

@nvkelso nvkelso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@zerebubuth zerebubuth merged commit 3971927 into master Dec 14, 2017
@zerebubuth zerebubuth deleted the zerebubuth/1406-include-all-name-variants branch December 14, 2017 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants