-
-
Notifications
You must be signed in to change notification settings - Fork 379
Feature/gsk 1243 project export doesnt work #1204
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
Conversation
GSK-1243 Project export doesn't work
|
…doesnt-work' into feature/gsk-1243-project-export-doesnt-work
|
Is this still WIP? I could review if it's ready and up-to-date |
|
@Inokinoki This PR needs to be updated with main, the export might be broken due to modification of database schema. It was initially on hold due to ongoing refactor of artifacts but we can merge it. |
|
@Inokinoki I've updated the branch and the export seems to be working with latest modification |
|
LGTM Could the 5 code smells in SonarLint be fixed as well? In addition, should we display something like "export failed" when getting 500 in frontend side? I can add it if you do not have time |
|
I tried to improve the code smell stuff from SonarLint. But I am not sure how to implement the comparison in the remaining one. |
…doesnt-work' into feature/gsk-1243-project-export-doesnt-work
Sure I fixed the error. In this case we had to override it to make sure two instance of |
|
Kudos, SonarCloud Quality Gate passed! |
|
LGTM |








Description
Related Issue
Type of Change
Checklist
CODE_OF_CONDUCT.mddocument.CONTRIBUTING.mdguide.make codestyle.