NOISSUE - Reconcile IDs to names in tables and inspect panels#4
Merged
Conversation
Signed-off-by: ianmuchyri <ianmuchiri8@gmail.com>
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
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.
What type of PR is this?
This is a feature because it improves readability across all admin tables and inspect panels by resolving UUIDs
to human-readable names.
What does this do?
useNameMaphook (lib/reconcile/use-name-map.ts) that resolves IDs to names in parallel, withsilent fallback to the raw ID on failure and 60s React Query caching
CrudTableandrenderCellfor the following fields:(when scope kind is
tenant)Which issue(s) does this PR fix/relate to?
N/A
Have you included tests for your changes?
No
Did you document any new/modified features?
No
Notes
All resolution is best-effort — if a lookup fails (deleted record, permission error), the raw ID is shown as
fallback. Requests for unique IDs on a page are fired in parallel so there is no sequential waterfall.