Proposal information - created/updated dates seem to be reversed
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 13
- Avg merge
- 1h 17m
- Merged PRs (30d)
- 1
Description
For the example v1/proposal/312064 endpoint on api-dev, the output shows:
(truncated)
{
"saf_id": "310638",
"status": "EXPIRED",
"instruments": [
"FMX"
]
}
],
"created_on": "2024-02-14T20:00:04.711216",
"last_updated": "2024-01-08T18:15:35.114000"
}
}
also, v1/beamline/name has similar output at the end:
"name": "xspress3",
"directory_name": "xspress3"
},
{
"name": "merlin",
"directory_name": "merlin"
}
],
"created_on": "2024-02-14T20:03:29.175304",
"last_updated": "2021-09-23T16:35:21.832000"
}
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Compare the response data for the v1/proposal/312064 and v1/beamline/name endpoints, focusing on their created_on and last_updated fields. Trace where those response fields are assembled and verify that each date has the correct meaning in the returned API output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fastapi, python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100