Skip to content

Conversation

@labkey-susanh
Copy link
Contributor

Rationale

Because we generally allow users to provide either the name of a field or its label during import, we should consistently be reserving both the name and the label for each domain so there will not be ambiguity when trying to resolve a column during import. This PR gets us closer to consistency by adding a utility method that will create the set of reservable strings given a field's name and then uses that in various domains, also making more of the reserved field sets static constants.

Related Pull Requests

Changes

  • Update getReservedPropertyNames with proper annotation.
  • Use static set for reserved names

@labkey-susanh labkey-susanh merged commit 3ecde2f into develop Sep 23, 2025
8 checks passed
@labkey-susanh labkey-susanh deleted the fb_reservedFields branch September 23, 2025 14:48
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