-
Notifications
You must be signed in to change notification settings - Fork 31
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
Bug in the IssuesTable component #208
Comments
Hey! @PedroHPAlmeida Is this why issues are not loading into the UI? I noticed in the API request it returns a I can take a look at this potentially if I have some time seeing as it has been open for a while. |
That's right, @Parsifal-M! |
Hey @PedroHPAlmeida 👋 Thanks for the heads up! I've raised a PR for this, hopefully, we can get it fixed. Cheers! |
Hi @PedroHPAlmeida and @Parsifal-M I suggest you to switch to the new official |
Ah, thanks for the heads up. 👍 |
In line 68 of the
IssuesTable.tsx
file a check is made to assign the variableprojectId
the value ofproject_id
(if it was passed as a parameter to the component), otherwise the value of theid
attribute of theprojectDetails
object is passed.The error occurs when the
project_id
parameter is not passed to the component and on line 70 the request is made by passing an undefined value. This happens when thecatalog-info.yaml
file has only thegitlab.com/project-slug
annotation.The solution is simple: just pass the variable
projectId
(notproject_id
) when calling the API, as is done in other components such asPipelinesTable.tsx
.The text was updated successfully, but these errors were encountered: