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.

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

Remove Reflect::Field::m_UIName #9

Open
gorlak opened this issue Aug 2, 2010 · 0 comments
Open

Remove Reflect::Field::m_UIName #9

gorlak opened this issue Aug 2, 2010 · 0 comments

Comments

@gorlak
Copy link
Member

gorlak commented Aug 2, 2010

We should not store a UI name separate from the field name. The field name doesn't need to be the same as the actual code name for the field, so the string literal passed into AddField should be the UI name, and there is only one name for a field. To handle cases where we want to rename a field to be more descriptive, we should add an aliasing system just like with types in the registry so that field queried with a legacy name still resolve.

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

No branches or pull requests

1 participant