Fix ACF REST field registration for built-in tags

[harugon]

WordPress uses "tag" as the additional REST fields object type for the built-in "post_tag" taxonomy.

ACF was registering built-in tag fields against the taxonomy name ("post_tag"), so the "acf" field was never exposed on /wp/v2/tags responses.

Register built-in tag fields against "tag" while preserving "post_tag" for internal ACF field-group matching in REST callbacks.

[gemini-code-assist]

Code Review

This pull request updates the ACF REST API to correctly handle WordPress term controllers. It maps the 'post_tag' taxonomy to the 'tag' REST object type during field registration and ensures taxonomy slugs are preserved when loading or updating fields for terms. The feedback suggests refactoring the duplicated logic for preserving taxonomy slugs into a private helper method to improve maintainability.

[gemini-code-assist]

This logic to preserve the taxonomy slug is also present in the load_fields method (lines 229-230). To avoid code duplication and improve maintainability, consider extracting this logic into a private helper method. This would ensure that any future changes to this logic only need to be made in one place.

[Copilot]

Pull request overview

Fixes ACF REST field registration for the built-in tag taxonomy by aligning ACF’s additional REST field object type with WordPress core’s term controller schema title (tag), while still using the taxonomy slug (post_tag) for ACF field-group matching during REST callbacks.

Changes:

• Register the acf REST field for built-in tags against the REST object type tag (instead of post_tag).
• Preserve the original taxonomy slug (post_tag) for field-group matching in load_fields() and update_fields() when handling term requests.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[harugon]

WordPress uses "tag" as the additional REST fields object type for the built-in "post_tag" taxonomy.

ACF was registering built-in tag fields against the taxonomy name ("post_tag"), so the "acf" field was never exposed on /wp/v2/tags responses.

Register built-in tag fields against "tag" while preserving "post_tag" for internal ACF field-group matching in REST callbacks.

[gemini-code-assist]

Code Review

This pull request updates the ACF REST API to correctly handle WordPress term controllers. It maps the 'post_tag' taxonomy to the 'tag' REST object type during field registration and ensures taxonomy slugs are preserved when loading or updating fields for terms. The feedback suggests refactoring the duplicated logic for preserving taxonomy slugs into a private helper method to improve maintainability.

[gemini-code-assist]

This logic to preserve the taxonomy slug is also present in the load_fields method (lines 229-230). To avoid code duplication and improve maintainability, consider extracting this logic into a private helper method. This would ensure that any future changes to this logic only need to be made in one place.

[Copilot]

Pull request overview

Fixes ACF REST field registration for the built-in tag taxonomy by aligning ACF’s additional REST field object type with WordPress core’s term controller schema title (tag), while still using the taxonomy slug (post_tag) for ACF field-group matching during REST callbacks.

Changes:

• Register the acf REST field for built-in tags against the REST object type tag (instead of post_tag).
• Preserve the original taxonomy slug (post_tag) for field-group matching in load_fields() and update_fields() when handling term requests.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[harugon]

WordPress uses "tag" as the additional REST fields object type for the built-in "post_tag" taxonomy.

ACF was registering built-in tag fields against the taxonomy name ("post_tag"), so the "acf" field was never exposed on /wp/v2/tags responses.

Register built-in tag fields against "tag" while preserving "post_tag" for internal ACF field-group matching in REST callbacks.

[gemini-code-assist]

Code Review

This pull request updates the ACF REST API to correctly handle WordPress term controllers. It maps the 'post_tag' taxonomy to the 'tag' REST object type during field registration and ensures taxonomy slugs are preserved when loading or updating fields for terms. The feedback suggests refactoring the duplicated logic for preserving taxonomy slugs into a private helper method to improve maintainability.

[gemini-code-assist]

This logic to preserve the taxonomy slug is also present in the load_fields method (lines 229-230). To avoid code duplication and improve maintainability, consider extracting this logic into a private helper method. This would ensure that any future changes to this logic only need to be made in one place.

[Copilot]

Pull request overview

Fixes ACF REST field registration for the built-in tag taxonomy by aligning ACF’s additional REST field object type with WordPress core’s term controller schema title (tag), while still using the taxonomy slug (post_tag) for ACF field-group matching during REST callbacks.

Changes:

• Register the acf REST field for built-in tags against the REST object type tag (instead of post_tag).
• Preserve the original taxonomy slug (post_tag) for field-group matching in load_fields() and update_fields() when handling term requests.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[harugon]

WordPress uses "tag" as the additional REST fields object type for the built-in "post_tag" taxonomy.

ACF was registering built-in tag fields against the taxonomy name ("post_tag"), so the "acf" field was never exposed on /wp/v2/tags responses.

Register built-in tag fields against "tag" while preserving "post_tag" for internal ACF field-group matching in REST callbacks.

[gemini-code-assist]

Code Review

This pull request updates the ACF REST API to correctly handle WordPress term controllers. It maps the 'post_tag' taxonomy to the 'tag' REST object type during field registration and ensures taxonomy slugs are preserved when loading or updating fields for terms. The feedback suggests refactoring the duplicated logic for preserving taxonomy slugs into a private helper method to improve maintainability.

[gemini-code-assist]

This logic to preserve the taxonomy slug is also present in the load_fields method (lines 229-230). To avoid code duplication and improve maintainability, consider extracting this logic into a private helper method. This would ensure that any future changes to this logic only need to be made in one place.

[Copilot]

Pull request overview

Fixes ACF REST field registration for the built-in tag taxonomy by aligning ACF’s additional REST field object type with WordPress core’s term controller schema title (tag), while still using the taxonomy slug (post_tag) for ACF field-group matching during REST callbacks.

Changes:

• Register the acf REST field for built-in tags against the REST object type tag (instead of post_tag).
• Preserve the original taxonomy slug (post_tag) for field-group matching in load_fields() and update_fields() when handling term requests.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[harugon]

WordPress uses "tag" as the additional REST fields object type for the built-in "post_tag" taxonomy.

ACF was registering built-in tag fields against the taxonomy name ("post_tag"), so the "acf" field was never exposed on /wp/v2/tags responses.

Register built-in tag fields against "tag" while preserving "post_tag" for internal ACF field-group matching in REST callbacks.

[gemini-code-assist]

Code Review

This pull request updates the ACF REST API to correctly handle WordPress term controllers. It maps the 'post_tag' taxonomy to the 'tag' REST object type during field registration and ensures taxonomy slugs are preserved when loading or updating fields for terms. The feedback suggests refactoring the duplicated logic for preserving taxonomy slugs into a private helper method to improve maintainability.

[gemini-code-assist]

This logic to preserve the taxonomy slug is also present in the load_fields method (lines 229-230). To avoid code duplication and improve maintainability, consider extracting this logic into a private helper method. This would ensure that any future changes to this logic only need to be made in one place.

[Copilot]

Pull request overview

Fixes ACF REST field registration for the built-in tag taxonomy by aligning ACF’s additional REST field object type with WordPress core’s term controller schema title (tag), while still using the taxonomy slug (post_tag) for ACF field-group matching during REST callbacks.

Changes:

• Register the acf REST field for built-in tags against the REST object type tag (instead of post_tag).
• Preserve the original taxonomy slug (post_tag) for field-group matching in load_fields() and update_fields() when handling term requests.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[harugon]

WordPress uses "tag" as the additional REST fields object type for the built-in "post_tag" taxonomy.

ACF was registering built-in tag fields against the taxonomy name ("post_tag"), so the "acf" field was never exposed on /wp/v2/tags responses.

Register built-in tag fields against "tag" while preserving "post_tag" for internal ACF field-group matching in REST callbacks.

[gemini-code-assist]

Code Review

This pull request updates the ACF REST API to correctly handle WordPress term controllers. It maps the 'post_tag' taxonomy to the 'tag' REST object type during field registration and ensures taxonomy slugs are preserved when loading or updating fields for terms. The feedback suggests refactoring the duplicated logic for preserving taxonomy slugs into a private helper method to improve maintainability.

[gemini-code-assist]

This logic to preserve the taxonomy slug is also present in the load_fields method (lines 229-230). To avoid code duplication and improve maintainability, consider extracting this logic into a private helper method. This would ensure that any future changes to this logic only need to be made in one place.

[Copilot]

Pull request overview

Fixes ACF REST field registration for the built-in tag taxonomy by aligning ACF’s additional REST field object type with WordPress core’s term controller schema title (tag), while still using the taxonomy slug (post_tag) for ACF field-group matching during REST callbacks.

Changes:

• Register the acf REST field for built-in tags against the REST object type tag (instead of post_tag).
• Preserve the original taxonomy slug (post_tag) for field-group matching in load_fields() and update_fields() when handling term requests.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[harugon]

WordPress uses "tag" as the additional REST fields object type for the built-in "post_tag" taxonomy.

ACF was registering built-in tag fields against the taxonomy name ("post_tag"), so the "acf" field was never exposed on /wp/v2/tags responses.

Register built-in tag fields against "tag" while preserving "post_tag" for internal ACF field-group matching in REST callbacks.

[gemini-code-assist]

Code Review

This pull request updates the ACF REST API to correctly handle WordPress term controllers. It maps the 'post_tag' taxonomy to the 'tag' REST object type during field registration and ensures taxonomy slugs are preserved when loading or updating fields for terms. The feedback suggests refactoring the duplicated logic for preserving taxonomy slugs into a private helper method to improve maintainability.

[gemini-code-assist]

This logic to preserve the taxonomy slug is also present in the load_fields method (lines 229-230). To avoid code duplication and improve maintainability, consider extracting this logic into a private helper method. This would ensure that any future changes to this logic only need to be made in one place.

[Copilot]

Pull request overview

Fixes ACF REST field registration for the built-in tag taxonomy by aligning ACF’s additional REST field object type with WordPress core’s term controller schema title (tag), while still using the taxonomy slug (post_tag) for ACF field-group matching during REST callbacks.

Changes:

• Register the acf REST field for built-in tags against the REST object type tag (instead of post_tag).
• Preserve the original taxonomy slug (post_tag) for field-group matching in load_fields() and update_fields() when handling term requests.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[harugon]

WordPress uses "tag" as the additional REST fields object type for the built-in "post_tag" taxonomy.

ACF was registering built-in tag fields against the taxonomy name ("post_tag"), so the "acf" field was never exposed on /wp/v2/tags responses.

Register built-in tag fields against "tag" while preserving "post_tag" for internal ACF field-group matching in REST callbacks.

[gemini-code-assist]

Code Review

This pull request updates the ACF REST API to correctly handle WordPress term controllers. It maps the 'post_tag' taxonomy to the 'tag' REST object type during field registration and ensures taxonomy slugs are preserved when loading or updating fields for terms. The feedback suggests refactoring the duplicated logic for preserving taxonomy slugs into a private helper method to improve maintainability.

[gemini-code-assist]

This logic to preserve the taxonomy slug is also present in the load_fields method (lines 229-230). To avoid code duplication and improve maintainability, consider extracting this logic into a private helper method. This would ensure that any future changes to this logic only need to be made in one place.

[Copilot]

Pull request overview

Fixes ACF REST field registration for the built-in tag taxonomy by aligning ACF’s additional REST field object type with WordPress core’s term controller schema title (tag), while still using the taxonomy slug (post_tag) for ACF field-group matching during REST callbacks.

Changes:

• Register the acf REST field for built-in tags against the REST object type tag (instead of post_tag).
• Preserve the original taxonomy slug (post_tag) for field-group matching in load_fields() and update_fields() when handling term requests.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.