-
Notifications
You must be signed in to change notification settings - Fork 33
Update frontend to match with release-jobs backend #1585
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
|
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.
Up to now I think the backend was backwards-compatible with v3. We should clearly indicate in the README that it requires scicat-backend-next.
fileList.push(d["archiveId"]); | ||
}); | ||
} | ||
fileObj.files = fileList; |
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.
We should discuss this change with some site that used the files
property.
This commit rebases and squashes SciCatProject#1585 (7d2a872). It contains the following commits: - update job view to match release-jobs - update job schema and timestamp fields - update jobs-detail page - fix testing and linting
* update job view to match release-jobs * update job schema and timestamp fields * update jobs-detail page * fix testing and linting
* update job view to match release-jobs * update job schema and timestamp fields * update jobs-detail page * fix testing and linting
Motivation
Make a first try to see whether the MVP
release-jobs
backend is compatible with the frontend.Description
To make the frontend compatible with the new Jobs schema from the
release-jobs
backend, we have to update the job list page, the job detail page, the schema in the frontend and all its references to it, as well as the.spec
test files.Fixes:
Changes:
src/app/shared/sdk/models/Job.ts
by updating the definition ofJob
classJob
class is created:datasetIds
insidejobParams
emailJobInitiator
tocreatedBy
and its value should beusername
instead ofemail
creationTime
tocreatedAt
jobs-dashboard-new.component
andjobs-detail.component
, so show in the job list and job details pages the new fields of the Job classjobs-dashboard.component
had to be updated too to avoid getting errors, but it appears to no longer be usedJob
class is created in one of the test filesBackend version
release-jobs