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.

Sign up for GitHub

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

Jump to bottom

Cache Initial API Calls for Query Blocks #218

Closed
efuller opened this issue Aug 16, 2024 · 0 comments · Fixed by #219
Closed

Cache Initial API Calls for Query Blocks #218

efuller opened this issue Aug 16, 2024 · 0 comments · Fixed by #219
Assignees
@efuller
Labels
enhancement New feature or request typescript Requires understanding TypeScript

Comments

@efuller
Copy link
Contributor

efuller commented Aug 16, 2024 •
edited
Loading

Summary

When loading a page that is powered by WP-Curate, for each query block, there is an API request that is made. We would like to find a way to optimize these API calls so that each block doesn't have to make the same calls.

Description

Use Case
@efuller efuller self-assigned this Aug 16, 2024
@efuller efuller mentioned this issue Aug 19, 2024
Merged
@kevinfodness kevinfodness added enhancement New feature or request typescript Requires understanding TypeScript labels Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@efuller efuller

Labels
enhancement New feature or request typescript Requires understanding TypeScript
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Feature: Issue-218: Cache Initial Post API Calls alleyinteractive/wp-curate
2 participants
@kevinfodness @efuller