Enhancements to Simplify Custom Schema Creation and Integration
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 6
Description
Pain Points
- Schema validation can be done only during measurement run.
- No IntelliSense or code completion for custom fields.
- High chance of typos or inconsistent field names due to lack of autocomplete.
Impact
- High likelihood of errors during development, especially when working with large or rapidly evolving schemas.
- Increased typos and field‑name inconsistencies due to the absence of autocomplete, validation, or guided tooling support.
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
The issue does not name files, tests, or entry points. First clarify the proposed custom-schema API, validation timing, and IntelliSense or completion scope with maintainers; then identify the affected Python API surfaces and define acceptance criteria for schema validation and field-name guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100