Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

translate_legacy_key vs translate_legacy_keys #6

Open
mbannert opened this issue Jan 31, 2018 · 1 comment
Open

translate_legacy_key vs translate_legacy_keys #6

mbannert opened this issue Jan 31, 2018 · 1 comment

Comments

@mbannert
Copy link
Member

@HomoCodens: why do we have 2 functions with almost the same name?
translate_legacy_key vs translate_legacy_keys

Do we need both?
@HomoCodens
Copy link
Collaborator

Good question, don't really know. Maybe one is a relic from a forgotten time.

I vote to keep translate_legacy_keys.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mbannert @HomoCodens