Migrate public api to new sessions/errors queries

[linear]

No description provided.

[linear]

HIG-4620 Migrate public api to new sessions/errors queries

[greptile-apps]

To migrate the public API to new sessions/errors queries, follow these steps based on the schema.resolvers.go file in the highlight/highlight repository:

1. Identify Existing Session and Error Query Resolvers: Review the current GraphQL schema definitions and resolver implementations related to sessions and errors. Look for functions like Session, ErrorGroup, and ErrorObject resolvers.

2. Define New GraphQL Queries: In your schema definition file (not provided), add new GraphQL query types for the sessions and errors that match your new requirements.

3. Implement New Resolvers: Based on the new query definitions, implement resolver functions in schema.resolvers.go. Use existing resolvers as a reference for accessing the database and formatting the response.

4. Update Resolver Functions: For sessions and errors, update the resolver functions to fetch and return data according to the new query parameters and structures. Refer to functions like Session, ErrorGroupResolver, and ErrorObjectResolver for patterns on handling database interactions and response formatting.

5. Test Your Changes: Ensure that your new queries and resolvers work as expected by writing and running tests. This step is crucial for validating the functionality and performance of the new API endpoints.

Remember to review and possibly refactor related parts of the codebase that might be affected by these changes, such as frontend queries or other backend services that consume the modified API.

References

highlight/highlight/backend/private-graph/graph/schema.resolvers.go
highlight/highlight/backend/private-graph/graph/generated/generated.go

Ask Greptile