Require wordpress/core-implementation and php as defined by the plugin

Open
#133 0 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go, php
Domain
backend

Research direction

The payload names no files, so start by finding where the Go code reads plugin headers and writes the generated package requirements. The change is to read the Requires PHP and Requires header fields and map them to a PHP constraint and a wordpress/core-implementation constraint. Settle the version-format questions with a maintainer first. Done means a plugin whose header declares these fields gets the matching requirements in its generated output, with a test covering it.

Written by the indexing model from the issue text.

Description

enhancement
Summary

This was requested for wpackgist (https://github.com/wpengine/wpackagist/issues/516) but would be extremely useful to have in wp-packages.

Proposed feature:

  • Read the plugin header
  • Extract Requires PHP and add it as a minimum PHP requirement
  • Extract Requires and use that to require a minimum wordpress/core-implementation
Additional context

No response

Dominant language
Go
Stars
146
Forks
9
Avg merge
5d 18h
Merged PRs (30d)
4

Getting set up

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 roots/wp-packages

All issues in roots/wp-packages

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.