Thanks to visit codestin.com
Credit goes to github.com

Skip to content

feat: add success notice after saving developer feature settings#807

Merged
dkotter merged 2 commits into
WordPress:developfrom
Infinite-Null:enhancement/developer-settings-success-notice
Jun 30, 2026
Merged

feat: add success notice after saving developer feature settings#807
dkotter merged 2 commits into
WordPress:developfrom
Infinite-Null:enhancement/developer-settings-success-notice

Conversation

@Infinite-Null

@Infinite-Null Infinite-Null commented Jun 30, 2026 •
edited by github-actions Bot
Loading

Copy link
Copy Markdown
Contributor

What?

Added visual confirmation (success snackbar) when saving or resetting AI developer settings.

Why?

Previously, users only received an error notice if a settings update failed, but there was no immediate visual feedback upon a successful save, unlike other places in the interface where a success snackbar is shown.

How?

  • Updated the useDeveloperFeatureSettings hook to import createSuccessNotice alongside createErrorNotice.
  • Inside the hook's save function, a success snackbar (Developer settings saved successfully.) is now dispatched.

Use of AI Tools

AI assistance: Yes
Tool(s): Claude 4.6 sonnet
Used for: Drafting this PR description.

Testing Instructions

  1. Navigate to the AI Settings page (/wp-admin/options-general.php?page=ai-wp-admin).
  2. Turn on Developer Mode.
  3. Change the Provider and Model selection, then click Save.
  4. Verify that a success snackbar appears.
  5. Click Reset to default.
  6. Verify that the settings reset and the success snackbar appears again.

Screenshots or screencast

Screen.Recording.2026-06-30.at.2.55.11.PM.mov

Changelog Entry

Changed - Added success snackbar when saving or resetting AI developer settings.

Open WordPress Playground Preview

@github-actions

github-actions Bot commented Jun 30, 2026

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: Infinite-Null <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@codecov

codecov Bot commented Jun 30, 2026 •
edited
Loading

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.48%. Comparing base (8da94a9) to head (a9c4275).

Additional details and impacted files 
@@            Coverage Diff             @@
##             develop     #807   +/-   ##
==========================================
  Coverage      76.48%   76.48%           
  Complexity      1869     1869           
==========================================
  Files             89       89           
  Lines           7990     7990           
==========================================
  Hits            6111     6111           
  Misses          1879     1879
Flag Coverage Δ
unit 76.48% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@dkotter dkotter added this to the 1.1.0 milestone Jun 30, 2026
@dkotter dkotter mentioned this pull request Jun 30, 2026
Closed
32 tasks
@dkotter dkotter merged commit 7678771 into WordPress:develop Jun 30, 2026
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@dkotter dkotter dkotter approved these changes

Assignees

@Infinite-Null Infinite-Null

Labels

None yet

Projects

None yet

Milestone

1.1.0

Development

Successfully merging this pull request may close these issues.

2 participants

@Infinite-Null @dkotter