Use pydantic instead of jsonschema for legacy project
Metadata
Current evaluation
Abandoned. Closed without implementation or associated pull request. The legacy codebase retains the pinned jsonschema dependency, and no migration to Pydantic models was executed.
Suggested action: —
No scores available.
Issue body
### What needs to get done
The legacy code for parsing the project should use Pydantic models instead of validating with the `jsonschema` library.
### Why it needs to get done
The current legacy code uses a pinned version of jsonschema that is very difficult to upgrade. Instead of upgrading, the code should just move over to using the more modern pydantic models.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. Closed without implementation or associated pull request. The legacy codebase retains the pinned jsonschema dependency, and no migration to Pydantic models was executed. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned without implementation. The legacy parsing code remains validated with jsonschema instead of migrating to Pydantic models as proposed. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. The migration from jsonschema to Pydantic for legacy project parsing was not implemented, and the issue was closed without follow-up or resolution. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation or discussion, indicating the task was abandoned. The legacy project parsing code remains unmodified. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without a linked resolution or pull request. The migration from jsonschema to Pydantic models for legacy project parsing was abandoned. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #5653 Use pydantic instead of jsonschema for legacy project | snapcraft | open | Migrate legacy snapcraft project parsing from jsonschema to Pydantic models. Issue was closed as abandoned, but the legacy code (snapcraft_legacy) has since been removed entirely from the codebase, making the issue moot. | |
| #5655 Use pydantic instead of jsonschema for legacy store | snapcraft | open | Enhancement to migrate legacy store response parsing (channel_map.py) from pinned jsonschema 2.6.0 to Pydantic models. Triaged by a maintainer with Jira ticket SNAPCRAFT-1203, but no activity for over a year; code at HEAD still uses jsonschema, so the work remains. | |
| #5230 Update jsonschema | snapcraft | open | Enhancement to update the ancient pinned jsonschema==2.6.0 dependency and fix breakages. Triaged by maintainers; the pin is still in pyproject.toml at HEAD, and the work is being pursued via follow-up issues replacing jsonschema with pydantic. |