-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat(dataverse-integration): add base classes and templates #190
feat(dataverse-integration): add base classes and templates #190
Conversation
jmurugan-fzj
commented
Jan 30, 2024
- Added the base UI files along with the extensions for the dataverse integration feature. Just added the basic UI files and the base classes with minimal/dummy functionality
- Added the backend thread-task extension for concurrent uploads in the background with an upload manager
- Added base database API for creating/retrieving documents/design documents/views etc. along with an extension for dataverse operations and database models
… integration feature - Added the backend thread-task extension for concurrent uploads in the background with an upload manager - Added base database API for creating/retrieving documents/design documents/views etc. along with an extension for dataverse operations and database models
- Code cleanup and refactoring
- Code cleanup and refactoring
- Code cleanup and refactoring
- Code cleanup and refactoring
@SteffenBrinckmann Could you please review this one, just all the basic classes needed are added even though the functionality is not as fully required, once the base classes are in, I will implement each functionality as separate PRs.. You could test this quickly in your system too, but the upload functionality is still showing dummy progress.. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you need all those libraries?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SteffenBrinckmann Without which this leads to the same error (github action "Verify Linux install / build ") what you have notice as part of your PR #195
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SteffenBrinckmann Sorry, I had removed all the un-necessary libs and included only Mesa 3D Graphics library which is needed by both the actions..
@SteffenBrinckmann Could you review and help me finalize this PR soon? |
@jmurugan-fzj could you look at the other two comments, that I had asked. A short answer suffices. |
@SteffenBrinckmann I see only one comment regarding the libs, are you sure you posted it or still in review? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this not part of the GUI, it requires Qt.... which is GUI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This only signals the UI with the data updates, does not directly do anything with UI or manage the UI items, only for signals, it's requires QT
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
line 107: should it not be doc['-type'][0] == 'x0'?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SteffenBrinckmann Good point, I changed the logic to check if the type includes 'x0', but why do we have the type defined as an array, does that mean that there is a possibility in PASTA to have any document with multiple entries for the type field? eg. doc['-type'] = ['x0', 'some_other_type', ..]?