WordPress / WordPress/secure-custom-fields
Implement alternative, unified file-based definitions
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 131
- Forks
- 64
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
Apart from being able to define CPTs, Taxonomies, and Field Groups in separate files (which map to the internal data structures), it should be possible to define a CPT and its fields directly in a single file, optimizing for the developer and LLM experience and absorbing the translation to the internal data layer.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name any files, tests, or entry points. Start by locating the existing separate-file definitions for CPTs, taxonomies, and field groups, then determine how a unified CPT-and-fields definition should translate into the internal data layer. Done means the proposed format and its integration are implemented and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100