You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I added a check to JobsService.updateJob() that will bypass job validation if the job is going from active to inactive. See: #3471. There were concerns that this could cause the job to end up in an invalid state.
It might be best to add a validation bypass flag to the post _inactive endpoint instead, so the user must actively decide to skip validation. Then setActiveState() could send that bypass argument to updateJob(), ensuring a typical api call to put _update could never skip validation.
The text was updated successfully, but these errors were encountered:
I added a check to
JobsService.updateJob()
that will bypass job validation if the job is going from active to inactive. See: #3471. There were concerns that this could cause the job to end up in an invalid state.It might be best to add a validation bypass flag to the
post _inactive
endpoint instead, so the user must actively decide to skip validation. ThensetActiveState()
could send that bypass argument toupdateJob()
, ensuring a typical api call toput _update
could never skip validation.The text was updated successfully, but these errors were encountered: