Skip to content

Commit a6671a7

Browse files
committed
Fix comment
1 parent 28d571e commit a6671a7

File tree

1 file changed

+3
-12
lines changed

1 file changed

+3
-12
lines changed

tests/e2e/plugins/scf-test-setup-post-types.php

Lines changed: 3 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -8,22 +8,13 @@
88
* @package wordpress/secure-custom-fields
99
*
1010
* IMPORTANT NOTE:
11-
* This plugin uses a hacky approach to create a test post type that SCF will recognize as its own:
11+
* This plugin uses a hacky approach to create a test post type that SCF will recognize as its own, don't replicate in production code:
1212
*
13-
* 1. We use SCF's internal APIs (acf_get_internal_post_type_instance) that aren't meant for public use
13+
* - We use SCF's internal APIs (acf_get_internal_post_type_instance) that aren't meant for public use
1414
* and could change between versions without notice.
1515
*
16-
* 2. We're directly creating database entries that SCF normally manages through its UI,
16+
* - We're directly creating database entries that SCF normally manages through its UI,
1717
* bypassing the normal workflow and validation that the UI might provide.
18-
*
19-
* 3. This approach requires intimate knowledge of SCF's internal data structures to know
20-
* exactly what fields the post type configuration needs.
21-
*
22-
* 4. The REST API endpoint determines SCF post types by calling acf_get_internal_post_type_posts(),
23-
* so we need to create a database entry that this function will return.
24-
*
25-
* This works for testing purposes but should NOT be considered a recommended pattern for
26-
* working with SCF in production environments.
2718
*/
2819

2920
// Exit if accessed directly

0 commit comments

Comments
 (0)