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

In a response to a query about an Issue, the URL and other info is missing for links created with Reference editor button #4093

Open
rudifa opened this issue May 17, 2024 · 4 comments

Comments

@rudifa
Copy link

rudifa commented May 17, 2024

In a github repo Issue there are 3 ways to insert a link to another issue, PR, e.t.c, for example:

#3231 - 2: same Reference not in a list

link - 3: a Link to the same url

Problem: in the response to a graphql query the link info is missing from the 2 Reference cases.

@rudifa
Copy link
Author

rudifa commented May 17, 2024

To reproduce the bug, send this query...

query {
  repository(owner: "graphql", name: "graphql-js") {
    issue(number: 4093) {
      title
      number
      body
    }
  }
}

... and examine the response, in which urls are missing in cases 1 and 2.

{
  "data": {
    "repository": {
      "issue": {
        "title": "In a response to a query about an Issue, the URL and other info is missing for links created with Reference editor button",
        "number": 4093,
        "body": "In a github repo **Issue** there are 3 ways to insert a link to another issue, PR, e.t.c, for example:\r\n\r\n- #3231 - 1: a Reference in a list\r\n\r\n#3231 - 2: same Reference not in a list\r\n\r\n[link](https://github.com/graphql/graphql-js/pull/3231) - 3: a Link to the same url\r\n\r\n**Problem**: in the response to a graphql query the **link info is missing** from the 2 Reference cases.\r\n"
      }
    }
  }
}

Moreover, here on the repo website, the case 1 also displays a git 'branch' icon and the title of the link target. These items are also missing from the response.

@rudifa
Copy link
Author

rudifa commented May 17, 2024

Actually, I am probably in a wrong place here, as this repo provides a js implementation of graphql spec.

The bug I'm trying to report is presumably in the github's implementation of their graphql server and its interaction with the github databases that store the repos and their issues.

Advice on where to go with this bug report would be appreciated.

@JoviDeCroock
Copy link

I do think this is the wrong place to ask that question, a good thing to check would be the description of the fields on issue maybe there's an option to make it output the links, if not I reckon the GitHub support staff is your best bet 😅

@rudifa
Copy link
Author

rudifa commented May 18, 2024

Thank you @JoviDeCroock.
In the meantime, I did open a ticket with the GitHub support.

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

No branches or pull requests

2 participants