Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pattern Creation: Make sure API fields are still connected correctly #376

Closed
2 tasks done
ryelle opened this issue Nov 10, 2021 · 0 comments
Closed
2 tasks done

Pattern Creation: Make sure API fields are still connected correctly #376

ryelle opened this issue Nov 10, 2021 · 0 comments
Assignees
Labels
[Component] Core/Gutenberg Changes that should happen in the core editor (tracking issues only) [Component] Pattern Directory API The pattern API on WordPress.org, and/or the CPT endpoint

Comments

@ryelle
Copy link
Contributor

ryelle commented Nov 10, 2021

Related to #33, we should also make sure the pattern keywords are correctly set from the API, having been changed from the taxonomy to a custom field.

  • Keywords are passed back from CPT API to proxy API (as meta.wpop_keywords)
  • Keywords are used when loading patterns into Gutenberg
@ryelle ryelle added the [Component] Pattern Directory API The pattern API on WordPress.org, and/or the CPT endpoint label Nov 10, 2021
@ryelle ryelle self-assigned this Jan 5, 2022
@ryelle ryelle added this to the Pattern Creation milestone Jan 13, 2022
@ryelle ryelle added the [Component] Core/Gutenberg Changes that should happen in the core editor (tracking issues only) label Jan 27, 2022
@ryelle ryelle removed this from the Pattern Creation milestone Feb 1, 2022
@ryelle ryelle closed this as completed Oct 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Component] Core/Gutenberg Changes that should happen in the core editor (tracking issues only) [Component] Pattern Directory API The pattern API on WordPress.org, and/or the CPT endpoint
Projects
None yet
Development

No branches or pull requests

1 participant