RESQ API - have data = null instead of empty object in response #536

Closed
opened 2021-02-10 08:21:24 +00:00 by jankstudio · 4 comments
jankstudio commented 2021-02-10 08:21:24 +00:00 (Migrated from gitlab.com)
No description provided.
jankstudio commented 2021-02-10 08:21:31 +00:00 (Migrated from gitlab.com)
created branch [`536-resq-api-have-data-null-instead-of-empty-object-in-response`](/jankstudio/resq/-/compare/master...536-resq-api-have-data-null-instead-of-empty-object-in-response) to address this issue
jankstudio commented 2021-02-10 09:07:32 +00:00 (Migrated from gitlab.com)

mentioned in commit eb675dd4b9

mentioned in commit eb675dd4b97cd44faac04badd569ba3ca4b537d7
jankstudio commented 2021-02-10 09:07:46 +00:00 (Migrated from gitlab.com)

mentioned in merge request !624

mentioned in merge request !624
jankstudio commented 2021-02-10 09:07:49 +00:00 (Migrated from gitlab.com)

mentioned in commit a021efea72

mentioned in commit a021efea729bea51f604e4ac4f2a017aeb79fde6
jankstudio (Migrated from gitlab.com) closed this issue 2021-02-10 09:07:49 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: rgutierrez/resq#536
No description provided.