Skip to content
This repository was archived by the owner on Jun 11, 2025. It is now read-only.

🎨 Updated gql and k8s-schema in infra and console#292

Merged
abdheshnayak merged 1 commit into
mainfrom
fix/update-gql-and-k8s-schema
Mar 6, 2024
Merged

🎨 Updated gql and k8s-schema in infra and console#292
abdheshnayak merged 1 commit into
mainfrom
fix/update-gql-and-k8s-schema

Conversation

@abdheshnayak
Copy link
Copy Markdown
Contributor

Updated k8s-schema and gql, because of types changes on operator.

@abdheshnayak abdheshnayak merged commit 7cd913b into main Mar 6, 2024
@abdheshnayak abdheshnayak deleted the fix/update-gql-and-k8s-schema branch March 6, 2024 07:53
Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

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

Hey abdheshnayak - Here's my review!

General suggestions:

  • Ensure that the refactoring does not introduce any regressions by thoroughly testing all affected resolvers.
  • Review the simplification of type declarations for clarity and maintainability.
  • Consider the broader impact of these changes on the system, especially in areas interacting with the updated schemas.

Thanks for using Sourcery. We offer it for free for open source projects and would be very grateful if you could help us grow. If you like it, would you consider sharing Sourcery on your favourite social media? ✨

Share Sourcery

Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.

metadataResolver struct{ *Resolver }
metadataInResolver struct{ *Resolver }
)
type github__com___kloudlite___api___common__CreatedOrUpdatedByResolver struct{ *Resolver }
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

suggestion (llm): Given the changes in types, it's crucial to ensure that the existing unit tests for these resolvers are updated to reflect the new type structures. If there are no existing tests, this is a good opportunity to add them to verify that the resolvers behave as expected with the updated types.

secretResolver struct{ *Resolver }
secretInResolver struct{ *Resolver }
)
type secretResolver struct{ *Resolver }
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

suggestion (llm): The refactoring of the secretResolver and secretInResolver types suggests a change in the underlying implementation. Please ensure that there are comprehensive tests covering these resolvers, particularly focusing on edge cases and error handling. If such tests are missing, consider adding them.

mutationResolver struct{ *Resolver }
queryResolver struct{ *Resolver }
)
type mutationResolver struct{ *Resolver }
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

suggestion (llm): The simplification of type declarations for mutationResolver and queryResolver indicates a structural change. It's important to verify through tests that these changes do not affect the functionality, especially for complex queries and mutations. Ensure that both positive and negative test cases are covered.

metadataResolver struct{ *Resolver }
metadataInResolver struct{ *Resolver }
)
type github__com___kloudlite___api___common__CreatedOrUpdatedByResolver struct{ *Resolver }
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

issue (llm): This pull request does not include modifications to test files. Given the nature of the changes, it's essential to ensure that the tests are aligned with the new type structures to prevent potential regressions. Please add or update tests accordingly.

abdheshnayak added a commit that referenced this pull request Nov 5, 2024
🎨 Updated gql and k8s-schema in infra and console
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant