Skip to content
This repository has been archived by the owner on May 2, 2022. It is now read-only.

Completely remove support for legacyName field #76

Open
bbqsrc opened this issue Dec 14, 2020 · 0 comments
Open

Completely remove support for legacyName field #76

bbqsrc opened this issue Dec 14, 2020 · 0 comments
Labels

Comments

@bbqsrc
Copy link
Member

bbqsrc commented Dec 14, 2020

If you let linguists have a field, they will cargo cult it into active use.

Remove the field, and add a hook in the iOS and Android generators to replace the ids with the legacy ids where necessary.

@bbqsrc bbqsrc added the bug label Dec 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant