-
Notifications
You must be signed in to change notification settings - Fork 6
promote main #963
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
base: main
Are you sure you want to change the base?
promote main #963
Conversation
…some of the fields/tables
Update api pagination metadata and documentation
Optimize get submissions api
Journal API Adjustments
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.
Bug: Inconsistent Error Handling in `assignSubmissionToEditor`
The assignSubmissionToEditor
function uses generic Error
for conditions that should use specific API error classes like ForbiddenError
or NotFoundError
. This is inconsistent with the error handling pattern established by other functions in the same file.
desci-server/src/services/journals/JournalSubmissionService.ts#L174-L175
nodes/desci-server/src/services/journals/JournalSubmissionService.ts
Lines 174 to 175 in 916139f
if (!chiefEditor) { | |
throw new Error('Only Chief editor is allowed to assign submissions'); |
desci-server/src/services/journals/JournalSubmissionService.ts#L186-L187
nodes/desci-server/src/services/journals/JournalSubmissionService.ts
Lines 186 to 187 in 916139f
if (submission.status !== SubmissionStatus.SUBMITTED) { | |
throw new Error('Submission is not in the submitted state'); |
Was this report helpful? Give feedback by reacting with 👍 or 👎
Remove OA prefix for OA data db switch
Journal API adjustments
Tay/kpi apis
fix: remove duplicate schema field
Misc C1 node fixes
Integration tests for KPI Metrics API
Warning We have to backfill legacyDpids as soon as we merge this
promote main