fix(website): use columns consistently in UI text - #91
Open
Bircck wants to merge 1 commit into
Open
Conversation
Fixes Azure DevOps bug 125339. Preserve internal identifiers and API names.
Bircck
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Metadata tabs, search placeholders and empty-result messages now consistently call Dataverse columns “columns”. Also updates the key heading, home-page copy, accessibility text and selection descriptions; internal identifiers and API names are unchanged.
Fixes inconsistent column terminology in the visible UI.
Validated with cached DMVPlayground metadata and Node 22.23.2: global/local matching and clearing, global and all local empty states, search tooltip, table tabs and home copy. Website lint and production build passed with existing warnings.