[FEATURE] Unify create_records and update_records server endpoints

[burtenshaw]

Is your feature request related to a problem? Please describe. Whilst refactoring the Python SDK, I am implementing methods to add and update records to Argilla server. When creating records, it is is possible to add suggestions and responses to the JSON body of the POST request. However, when updating records via the PATCH method, it is only possible to add suggestions to the body.

Describe the solution you'd like Ideally, both responses and suggestions could be passed in the body update and create endpoints.

Create Records Update Records

Describe alternatives you've considered This would also be possible via the /api/v1/me/responses/bulk endpoint, or individually calling /api/v1/records/{record_id}/responses.

[dosubot[bot]]

It's great to see your interest in improving the server endpoints! Your proposed solution to unify the create_records and update_records endpoints sounds like a valuable enhancement. We encourage you to go ahead and create a pull request with your proposed changes. Your contribution will be much appreciated by the community. Thank you for your initiative!

About Dosu

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 30 days since being marked as stale.