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

fix: Introspection OrderArg returns null inputFields #1633

Merged
merged 4 commits into from
Jul 13, 2023

Conversation

nasdf
Copy link
Member

@nasdf nasdf commented Jul 12, 2023

Relevant issue(s)

Resolves #1632
Resolves #1502
Resolves #1463

Description

This PR adds an introspection test that identifies an issue with orderArg.

Tasks

  • I made sure the code is well commented, particularly hard-to-understand areas.
  • I made sure the repository-held documentation is changed accordingly.
  • I made sure the pull request title adheres to the conventional commit style (the subset used in the project can be found in tools/configs/chglog/config.yml).
  • I made sure to discuss its limitations such as threats to validity, vulnerability to mistake and misuse, robustness to invalidation of assumptions, resource requirements, ...

How has this been tested?

make test

Specify the platform(s) on which this was tested:

  • MacOS

map[string]any{
"name": "members",
"type": map[string]any{
"name": "",
Copy link
Member Author

Choose a reason for hiding this comment

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

I think this may be the root of the issue. The name should not be empty.

@nasdf nasdf changed the title fix: Introspection OrderArg returns null inputFields fix: Introspection OrderArg returns null inputFields Jul 13, 2023
@codecov
Copy link

codecov bot commented Jul 13, 2023

Codecov Report

Patch coverage: 100.00% and project coverage change: -0.13 ⚠️

Comparison is base (9611024) 75.61% compared to head (689cd65) 75.48%.

Impacted file tree graph

@@             Coverage Diff             @@
##           develop    #1633      +/-   ##
===========================================
- Coverage    75.61%   75.48%   -0.13%     
===========================================
  Files          199      199              
  Lines        20774    20769       -5     
===========================================
- Hits         15707    15676      -31     
- Misses        3992     4009      +17     
- Partials      1075     1084       +9     
Flag Coverage Δ
all-tests 75.48% <100.00%> (-0.13%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
request/graphql/schema/generate.go 85.46% <100.00%> (-0.08%) ⬇️

... and 9 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9611024...689cd65. Read the comment docs.

@fredcarle fredcarle added the bug Something isn't working label Jul 13, 2023
@nasdf nasdf marked this pull request as ready for review July 13, 2023 18:25
@nasdf nasdf requested a review from a team July 13, 2023 18:25
Copy link
Collaborator

@fredcarle fredcarle left a comment

Choose a reason for hiding this comment

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

Great investigative work on this one Keenan.

I'm pretty sure this PR also resolves #1502 and #1463 so you could add them to the set of resolved issues in the PR description.

@nasdf nasdf merged commit 808d6be into sourcenetwork:develop Jul 13, 2023
10 checks passed
@nasdf nasdf deleted the nasdf/fix/introspection-order-arg branch July 13, 2023 22:37
shahzadlone pushed a commit to shahzadlone/defradb that referenced this pull request Feb 23, 2024
)

## Relevant issue(s)

Resolves sourcenetwork#1632 
Resolves sourcenetwork#1502 
Resolves sourcenetwork#1463

## Description

This PR adds an introspection test that identifies an issue with
`orderArg`.

## Tasks

- [x] I made sure the code is well commented, particularly
hard-to-understand areas.
- [x] I made sure the repository-held documentation is changed
accordingly.
- [x] I made sure the pull request title adheres to the conventional
commit style (the subset used in the project can be found in
[tools/configs/chglog/config.yml](tools/configs/chglog/config.yml)).
- [x] I made sure to discuss its limitations such as threats to
validity, vulnerability to mistake and misuse, robustness to
invalidation of assumptions, resource requirements, ...

## How has this been tested?

`make test`

Specify the platform(s) on which this was tested:
- MacOS
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
2 participants