Skip to content

Reference json uses employer_name instead of employer #44

@jbutcher21

Description

@jbutcher21

FYI it still detects its the employer feature, and makes the usage type name. Early on we allowed the usage type to be either before or after. HOME_PHONE_NUMBER or PHONE_NUMBER_HOME both work!

Still it should be removed to make the intent clear.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions