WordPress / WordPress/secure-custom-fields
Migration of old APIs and filenames to SCF namespace
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 131
- Forks
- 64
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
As time evolves, SCF is likely to diverge from the ACF parent, and it should be considered how to adapt the existing codebase to a new namespace.
There is an initial attempt at adding a legacy mode in #92. However, we need to study the pros and cons of any action we take to divert from ACF, as the more the codebases diverge, the more challenging it is to backport security patches across both versions, which is in the interest of both user bases.
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
Review the initial legacy-mode attempt in #92 and compare the existing ACF and SCF APIs and filenames. Assess the pros and cons of namespace divergence, especially the difficulty of backporting security patches; done means an agreed migration or non-migration plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100