We used to export a single task from server-side to the mw.config object using a 'task-preview' structure. In T308542: Suggested edits: Populate task queue from server-side we exported the entire task queue. There's no longer a reason to create a special task-preview object; instead, we should just take the first item from the task-queue.
Acceptance Criteria
- References to task-preview are gone from the codebase
- Code needing to access the first task in the queue access it from task-queue
Completion checklist
Functionality
- The patches have been code reviewed and merged
- The task passes its acceptance criteria
Engineering
- There are existing and passing unit/integration tests
- Tests for every involved patch should pass
- Coverage for every involved project should have improved or stayed the same
Design & QA
- If the task is UX/Design related: it must be reviewed and approved by the UX/Design team
- Must be reviewed and approved by Quality Assurance.
Documentation
- Related and updated documentation done where necessary
- Internal technical changes: internal repository documentation must be updated (README.md, JSDoc, PHPDoc)
- Infrastructure technical changes: technical changes that reflect on environment, infrastructure, endpoints or any other area of interest for technical contributors should be reflected on Extension:GrowthExperiments or Extension:GrowthExperiments/Technical documentation pages.