Fix: Endpoint URL field is not a URL type field #3733
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
burhandodhy
force-pushed
the
fix/endpoint-url-field-is-not-type-url
branch
from
c78d23b
to
810cdaf
Compare
burhandodhy
changed the title
JakePT
approved these changes
Oct 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the Change
This PR fixes an issue where the Endpoint URL field is not a URL type field on the features page, even though its set a URL type field in the schema https://github.com/10up/ElasticPress/blob/5.0.0/includes/classes/Feature/Autosuggest/Autosuggest.php#L911
Closes #
How to test the Change
Changelog Entry
Credits
Props @burhandodhy
Checklist: