Don't use XSLT in report generator

Open
#909 18 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
json, python, xml
Domain
tooling

Research direction

Start by locating the report generator and reviewing how it uses XSLT. Compare the existing approach with the issue's suggested alternatives, straight XML manipulation or JSON, and define the replacement's scope before changing anything. Done means the report generator no longer relies on XSLT and its output remains covered by the project's existing checks.

Written by the indexing model from the issue text.

Description

priority-1-normal refactoring

XSLT is not a widely used technology and pretty complex (and I don't want to learn it). We shouldn't rely on it in the report generator. Some reasonable alternatives include straight XML manipulation or JSON.

Dominant language
Python
Stars
20.6k
Forks
3.3k
Avg merge
1d 18h
Merged PRs (30d)
54

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/mypy

All issues in python/mypy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.