Medical-Event-Data-Standard / Medical-Event-Data-Standard/flexible_schema
It would be nice to be able to support specifying preferred field order
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
See attached branch for starting code.
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.
Research direction
Start by inspecting the attached branch and locating the metaclass or schema entry point it changes. Determine how field definitions are currently collected and where ordering is established. Done should mean the schema can accept a preferred field order while preserving existing validation and column behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100