Let's revisit this approach to leverage pydantic constructors and validators.
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 13
- Avg merge
- 1h 17m
- Merged PRs (30d)
- 1
Description
Let's revisit this approach in a future PR, where we could leverage pydantic constructors and validators.
I'll move this comment to a GH issue momentarily.
Originally posted by @padraic-shafer in https://github.com/NSLS2/nsls2api/pull/212#discussion_r2722862103
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
The issue names no files, tests, or entry points to inspect. First clarify which existing approach should be revisited and which Pydantic constructors or validators are in scope; define the expected behavior and tests before starting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100