Skip to content

Refresh features on save#4275

Open
ZacharyRener wants to merge 10 commits intodevelopfrom
fix/stale-interface-feature-dependency
Open

Refresh features on save#4275
ZacharyRener wants to merge 10 commits intodevelopfrom
fix/stale-interface-feature-dependency

Conversation

@ZacharyRener
Copy link
Collaborator

@ZacharyRener ZacharyRener commented Jan 23, 2026

Description of the Change

The purpose with this PR is to refresh the feature settings and settings schema on save, instead of requiring a refresh, universally.

For SemanticSearch in particular, EP Labs needs an update to actually consider whether the feature is active before adding the algorithms: 10up/ElasticPressLabs#184

For testing, see 10up/ElasticPressLabs#184

You can also reference the feature interface e2e test added here which has a simulated version of this

Closes #4267

How to test the Change

  • Enable Semantic Search
  • Enable a semantic search algorithm version
  • Save settings
  • Go to Instant Results
  • Confirm it is now showing as disabled without refreshing the page

Changelog Entry

Changed - Saving feature settings will now reflect feature dependency without refreshing the page

Credits

Props @ZacharyRener

Checklist:

@ZacharyRener ZacharyRener marked this pull request as ready for review January 26, 2026 17:16
Copy link
Member

@felipeelia felipeelia left a comment

Choose a reason for hiding this comment

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

@ZacharyRener any chance we can add some e2e tests for this one? Enabling Did you mean should make an option in Instant Results editable, for example.

@ZacharyRener
Copy link
Collaborator Author

@felipeelia The staleness issue happens when the TEMPORARILY_DISABLED status is passed (or similar server side check), because those server side checks weren't applying until page refresh. The did you mean / instant results example you already doesn't go stale because it's just an interface check

EP labs example

So I setup a test plugin here to simulate the conflict and added an e2e test

I'll move this to review once the tests are all passing but just fyi.

@felipeelia felipeelia added this to the 5.3.3 milestone Feb 12, 2026
@ZacharyRener
Copy link
Collaborator Author

ZacharyRener commented Feb 26, 2026

The purpose with this PR now is to refresh the feature settings and settings schema on save, instead of requiring a refresh, universally. The test here was updated to be a more generic replication of the issue instead of the temporarily_disabled check from earlier.

For SemanticSearch in particular, EP Labs needs an update to actually consider whether the feature is active before adding the algorithms: 10up/ElasticPressLabs#184

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.

Reload settings panel on save

2 participants