Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GraphQL type check perf fix #43852

Merged
merged 6 commits into from
Feb 28, 2025
Merged

GraphQL type check perf fix #43852

merged 6 commits into from
Feb 28, 2025

Conversation

heshanpadmasiri
Copy link
Member

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues.

Fixes #

Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

  • Read the Contributing Guide
  • Updated Change Log
  • Checked Tooling Support (#)
  • Added necessary tests
    • Unit Tests
    • Spec Conformance Tests
    • Integration Tests
    • Ballerina By Example Tests
  • Increased Test Coverage
  • Added necessary documentation
    • API documentation
    • Module documentation in Module.md files
    • Ballerina By Examples

Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

@heshanpadmasiri heshanpadmasiri changed the title [WIP] GraphQL type check perf fix GraphQL type check perf fix Feb 27, 2025
@heshanpadmasiri heshanpadmasiri marked this pull request as ready for review February 27, 2025 15:15
@gimantha gimantha merged commit f38db34 into 2201.12.x Feb 28, 2025
16 of 17 checks passed
@heshanpadmasiri heshanpadmasiri deleted the fix/graphql-perf branch February 28, 2025 07:00
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.

2 participants