Cannot relate attachement through datasetId field in POST request of attachments v4
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
Research direction
Start by tracing the POST /api/v4/attachments entry point and its request validation to see why datasetId is rejected. Then follow attachment creation and dataset relation handling; done means a request containing datasetId is accepted and the attachment is associated with the existing dataset rather than created without a relation.
Written by the indexing model from the issue text.
Description
Summary
When trying to attach an attachment to an existing dataset, one cannot indicate the dataset to which the attachment belongs. It seemed possible in v3.
Steps to Reproduce
Post an attachment using /api/v4/attachments
Current Behaviour
returns {
"message": [
"property datasetId should not exist"
],
"error": "Bad Request",
"statusCode": 400
}
After removing this field, it returns a 201 so the attachment was created but ends in nirvana.
- Dominant language
- TypeScript
- Stars
- 27
- Forks
- 37
- Avg merge
- 17h 32m
- Merged PRs (30d)
- 38
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from SciCatProject/backend
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
SciCatProject/backend#1998 ·
-
SciCatProject/backend#2961 · 1 reaction · 5 assignees ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
SciCatProject/backend#2923 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
SciCatProject/backend#2901 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
SciCatProject/backend#2900 ·
All issues in SciCatProject/backend
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·