Skip to content

pr: [Nightly Fix] - Typo - Polish User Facing Copy#7

Open
jewel-claw wants to merge 1 commit intomasterfrom
nightly-fix/user-facing-typos
Open

pr: [Nightly Fix] - Typo - Polish User Facing Copy#7
jewel-claw wants to merge 1 commit intomasterfrom
nightly-fix/user-facing-typos

Conversation

@jewel-claw
Copy link

What

  • clean up a few awkward user-facing strings in the plugin UI

Why

  • the empty-state message is grammatically off
  • the deactivation feedback prompt reads awkwardly and looks unpolished in admin

Fix

  • change No Result Found to No Results Found
  • rewrite the deactivation prompt to Please share any suggestions so we can improve.

Confidence

  • linted app/Hooks/Handlers/DeactivationHandler.php and app/Modules/DataProviders/NinjaFooTable.php with php -l

@greptile-apps
Copy link

greptile-apps bot commented Mar 10, 2026

PR author is not in the allowed authors list.

@qodo-code-review
Copy link

ⓘ You are approaching your monthly quota for Qodo. Upgrade your plan

Review Summary by Qodo

Polish user-facing copy and fix grammatical errors

✨ Enhancement

Grey Divider

Walkthroughs

Description
• Fix grammatical error: "No Result Found" → "No Results Found"
• Improve deactivation feedback prompt clarity and professionalism
• Polish user-facing copy in plugin UI for better UX
Diagram
flowchart LR
  A["User-facing strings"] -->|"Fix grammar"| B["No Results Found"]
  A -->|"Improve clarity"| C["Deactivation prompt"]
  B --> D["NinjaFooTable.php"]
  C --> E["DeactivationHandler.php"]
Loading

Grey Divider

File Changes

1. app/Hooks/Handlers/DeactivationHandler.php ✨ Enhancement +1/-1

Improve deactivation feedback prompt wording

• Updated deactivation feedback prompt from "Kindly tell us any suggestion so we can improve" to
 "Please share any suggestions so we can improve."
• Improved tone and professionalism of the custom label text

app/Hooks/Handlers/DeactivationHandler.php


2. app/Modules/DataProviders/NinjaFooTable.php ✨ Enhancement +2/-2

Fix grammar in empty state message

• Changed empty state message from "No Result Found" to "No Results Found" in two locations
• Fixed grammatical error in localized string for better user experience
• Updated both the asset localization and table rendering functions

app/Modules/DataProviders/NinjaFooTable.php


Grey Divider

Qodo Logo

@qodo-code-review
Copy link

qodo-code-review bot commented Mar 10, 2026

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider


Action required

1. Broken translation lookup 🐞 Bug ✓ Correctness
Description
The msgid was changed to "No Results Found" in NinjaFooTable, but the shipped translation catalogs
still contain "No Result Found", so WordPress will not find a translation and will fall back to
English on localized sites.
Code

app/Modules/DataProviders/NinjaFooTable.php[76]

+                'empty_text'     => __('No Results Found', 'ninja-tables'),
Evidence
Runtime now requests translations for a new msgid, but the repo’s .pot/.po catalogs still define
only the old msgid. Since the framework loads the plugin textdomain from /language via
load_plugin_textdomain(), the msgid mismatch prevents translation lookup and returns the raw English
string.

app/Modules/DataProviders/NinjaFooTable.php[69-79]
app/Modules/DataProviders/NinjaFooTable.php[378-385]
language/ninja-tables.pot[599-603]
language/ninja-tables-es.po[530-534]
vendor/wpfluent/framework/src/WPFluent/Foundation/Application.php[273-286]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The code now translates a new msgid (`"No Results Found"`), but the repo-shipped translation catalogs still contain only the old msgid (`"No Result Found"`). This causes translation lookup failures and English fallback on localized sites.

### Issue Context
This plugin loads translations from `/language` via `load_plugin_textdomain()`, so msgid mismatches directly break localization.

### Fix Focus Areas
- app/Modules/DataProviders/NinjaFooTable.php[69-79]
- app/Modules/DataProviders/NinjaFooTable.php[378-385]
- language/ninja-tables.pot[599-603]
- language/ninja-tables-es.po[530-534]
- vendor/wpfluent/framework/src/WPFluent/Foundation/Application.php[273-286]

### Implementation notes
- Update `language/ninja-tables.pot` to replace/add msgid `"No Results Found"`.
- Update each shipped `language/*.po` to include `msgid "No Results Found"` with an appropriate translation, then recompile the corresponding `language/*.mo`.
- Ensure the old msgid entry is removed or left only if still used elsewhere.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools



Remediation recommended

2. Prompt remains untranslatable 🐞 Bug ✓ Correctness
Description
The updated deactivation reason prompt is still hard-coded (not wrapped in translation functions)
and is rendered directly in the admin deactivation modal, so localized sites will always see English
for this prompt.
Code

app/Hooks/Handlers/DeactivationHandler.php[108]

+                "custom_label"       => 'Please share any suggestions so we can improve.',
Evidence
The PR updates the string content, but the value is still a raw PHP string that bypasses the
plugin’s i18n mechanism, and the view prints it as-is into the modal UI.

app/Hooks/Handlers/DeactivationHandler.php[96-121]
app/Views/admin/deactivate-form.php[20-27]
vendor/wpfluent/framework/src/WPFluent/Foundation/Application.php[273-286]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The deactivation feedback prompt text is user-facing but is hard-coded and not translatable, so localized WordPress admins will always see English.

### Issue Context
This is not newly introduced by this PR (the strings were already hard-coded), but the PR changes the prompt content and continues the non-translatable pattern.

### Fix Focus Areas
- app/Hooks/Handlers/DeactivationHandler.php[96-121]
- app/Views/admin/deactivate-form.php[20-27]
- vendor/wpfluent/framework/src/WPFluent/Foundation/Application.php[273-286]

### Implementation notes
- Change `"custom_label" => 'Please share...'` to `"custom_label" => __('Please share any suggestions so we can improve.', 'ninja-tables')` (and similarly for the other user-facing strings in that reasons array).
- Consider using `esc_html__()` at render sites if you want escaping + translation in one call.
- Regenerate/update `language/ninja-tables.pot` and shipped translations if you distribute them.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

ⓘ The new review experience is currently in Beta. Learn more

Grey Divider

Qodo Logo

@kilo-code-bot
Copy link

kilo-code-bot bot commented Mar 10, 2026

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (2 files)
  • app/Hooks/Handlers/DeactivationHandler.php - Grammar fix in deactivation feedback prompt
  • app/Modules/DataProviders/NinjaFooTable.php - Grammar fix in "No Results Found" text (2 locations)

Notes: This PR corrects grammatical errors in user-facing text:

  • "No Result Found" → "No Results Found" (proper plural form)
  • "Kindly tell us any suggestion" → "Please share any suggestions" (grammatical and professional tone)

These are minor text improvements that enhance the user experience. No code issues found that would block merging.

'search_in' => __('Search in', 'ninja-tables'),
'search' => __('Search', 'ninja-tables'),
'empty_text' => __('No Result Found', 'ninja-tables'),
'empty_text' => __('No Results Found', 'ninja-tables'),

Choose a reason for hiding this comment

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

Action required

1. Broken translation lookup 🐞 Bug ✓ Correctness

The msgid was changed to "No Results Found" in NinjaFooTable, but the shipped translation catalogs
still contain "No Result Found", so WordPress will not find a translation and will fall back to
English on localized sites.
Agent Prompt
### Issue description
The code now translates a new msgid (`"No Results Found"`), but the repo-shipped translation catalogs still contain only the old msgid (`"No Result Found"`). This causes translation lookup failures and English fallback on localized sites.

### Issue Context
This plugin loads translations from `/language` via `load_plugin_textdomain()`, so msgid mismatches directly break localization.

### Fix Focus Areas
- app/Modules/DataProviders/NinjaFooTable.php[69-79]
- app/Modules/DataProviders/NinjaFooTable.php[378-385]
- language/ninja-tables.pot[599-603]
- language/ninja-tables-es.po[530-534]
- vendor/wpfluent/framework/src/WPFluent/Foundation/Application.php[273-286]

### Implementation notes
- Update `language/ninja-tables.pot` to replace/add msgid `"No Results Found"`.
- Update each shipped `language/*.po` to include `msgid "No Results Found"` with an appropriate translation, then recompile the corresponding `language/*.mo`.
- Ensure the old msgid entry is removed or left only if still used elsewhere.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

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