Refactor entity count formatting to support translations #1477
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.
Description
This PR refactors entity count formatting from a static utility function into a custom hook that properly integrates with the translation system, enabling query-language-specific terminology.
New Hook:
useEntityCountFormatterCreated a new hook that replaces the static
formatEntityCountsutility with translation-aware formatting:useFormattedEntityCounts(vertexCount, edgeCount)- Direct formatting hook for use in componentsuseEntityCountFormatterCallback()- Returns a callback function for use in mutations and async operationsKey improvements:
Updated Components
GraphViewerEmptyState- Now usesuseFormattedEntityCountshookImportGraphButton- Now usesuseEntityCountFormatterCallbackfor mutation callbacksuseRestoreGraphSession- Now usesuseEntityCountFormatterCallbackfor mutation callbacksThis change ensures that entity count messages throughout the application respect the active query language's terminology.
Validation
Gremlin
Cypher
SPARQL
Related Issues
Check List
license.
pnpm checksto ensure code compiles and meets standards.pnpm testto check if all tests are passing.Changelog.md.