Deprecate specific task parser

Open
#180 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start by locating the task parser and the analyzers or review code that consume its payloads. Trace how the current task format is handled, then identify the expected new default format and the compatibility period. Done means the specific task parser is deprecated while both current and new payloads remain supported during rebases.

Written by the indexing model from the issue text.

Description

bot

As the analyzers will use the new default format, we should deprecate the different tasks.
We'll also need to support current & new payload for a time (while all the review get rebased on recent bases).

Dominant language
Python
Stars
67
Forks
52
Avg merge
3d 23h
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 mozilla/code-review

All issues in mozilla/code-review

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.