Skip to content

Conversation

cmwhited
Copy link
Collaborator

Description

Note this is an initial change to use the v2 indexer endpoint. The goal was to update the gql codegen and the current queries to use the new endpoint/schema. This change will not be published to npm.

I am working on follow up PR(s) to make the type/property resolution much more robust in typesync (and handle searching, etc). But wanted to make this change first.

@cmwhited cmwhited requested a review from baiirun July 15, 2025 19:42
Comment on lines +11 to +12
query SchemaBrowserTypes($first: Int) {
typesList(first: $first) {
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO: come up with a better way to select an initial set of types to render, then let users search knowledge graph after

Comment on lines +170 to +171
query Properties($first: Int) {
properties(first: $first) {
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here. @baiirun @yanivtal thoughts on "best" way to query for a like "most used" set of properties we would want to render first?

@cmwhited cmwhited merged commit bea0602 into main Jul 17, 2025
6 checks passed
@cmwhited cmwhited deleted the chris.whited/typesync/v2-type-endpoint branch July 17, 2025 00:59
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.

1 participant