Skip to content

Added: save _edac_summary_content_grade as individual post meta#1600

Open
SteveJonesDev wants to merge 1 commit intodevelopfrom
PRO-423
Open

Added: save _edac_summary_content_grade as individual post meta#1600
SteveJonesDev wants to merge 1 commit intodevelopfrom
PRO-423

Conversation

@SteveJonesDev
Copy link
Copy Markdown
Member

@SteveJonesDev SteveJonesDev commented Mar 25, 2026

This pull request makes a minor update to the summary metadata saving function. It now also saves the content_grade value to the post meta data, ensuring this additional piece of information is stored alongside other summary details.

  • Added saving of the content_grade value to post meta in the save_summary_meta_data function in class-summary-generator.php.

Summary by CodeRabbit

  • Bug Fixes
    • Content grade scores are now properly persisted and stored alongside other assessment metrics for improved data retention.

Saves the content grade as a flat meta key alongside the existing
individual summary meta keys, enabling numeric sorting of the new
Reading Level admin column in Accessibility Checker Pro.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the data persistence for post summaries by adding a new metric, content_grade, to the stored metadata. This ensures that a more complete set of summary information is available for future use and analysis.

Highlights

  • Summary Metadata Saving: The save_summary_meta_data function now includes the content_grade value when saving post meta data, ensuring this specific metric is persistently stored.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 25, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: dcf3eedc-a0f6-42fb-85fb-07f02f81fd54

📥 Commits

Reviewing files that changed from the base of the PR and between 7b6ef1f and b908aa1.

📒 Files selected for processing (1)
  • includes/classes/class-summary-generator.php

📝 Walkthrough

Walkthrough

The pull request extends the summary generation metadata storage to persist the computed content_grade value to post metadata alongside existing summary metrics, using the _edac_summary_content_grade meta key.

Changes

Cohort / File(s) Summary
Summary Metadata Persistence
includes/classes/class-summary-generator.php
Extended save_summary_meta_data() to persist content_grade value as _edac_summary_content_grade post meta.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested labels

codex

Poem

🐰 A whisker of metadata,
Stored with care so neat,
Content grades now flourish,
In persistence, oh so sweet!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly and specifically describes the main change: saving the content_grade value as an individual post meta field.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch PRO-423

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds functionality to save the content_grade as post meta data, specifically _edac_summary_content_grade, within the save_summary_meta_data function in class-summary-generator.php. There is no feedback to provide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant