chore {Performance}: Implement models for Blocks

Open
#385 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
graphql, php, wordpress

Research direction

Start with issue #378 and the referenced experiment PR to understand the intended WPGraphQL Models approach. Compare the prior art in wp-rest-blocks/src/data.php and snapwp-helper/src/Modules/GraphQL/SchemaFilters.php. Done means block rendering uses models that can be cached and reused, with the intended performance improvement demonstrated.

Written by the indexing model from the issue text.

Description

effort: high impact: high scope: performance

Overview

See #378

Long term goal is to improve performance of block rendering by creating WPGraphQL Models instead on a field level so blocks can be cached and re-used.

References

Dominant language
PHP
Stars
149
Forks
16
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wpengine/wp-graphql-content-blocks

All issues in wpengine/wp-graphql-content-blocks

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.