Update terminology: "Graph Type" → "Query Language" #1474
Merged
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 updates user-facing terminology throughout the application to use "Query Language" instead of "Graph Type" for better clarity and accuracy.
Changes
UI Updates:
Translation System:
graph-typetoquery-languageacross all three translation files (Gremlin, openCypher, SPARQL)query-languagekeyDocumentation Updates:
Test Updates:
ImportGraphButton.test.tsxto match new terminologyuseEdgeAttributesAsScalars.test.tswith separate test suites for Gremlin and openCypher to verify correct terminology ("Edge Label" vs "Relationship Type")Rationale
"Query Language" more accurately describes what users are selecting (Gremlin, openCypher, or SPARQL) rather than the ambiguous "Graph Type" which could be confused with the data model (property graph vs RDF).
Validation
Related Issues
Check List
license.
pnpm checksto ensure code compiles and meets standards.pnpm testto check if all tests are passing.Changelog.md.