APIv4 - Don't link to non-existent API entities #25743
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
|
(Standard links)
|
|
I've hit variants of this a lot so yay to merge - style issue to fix
|
|
retest this please |
|
civibot, test this please |
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.
Overview
Fixes bug described in https://lab.civicrm.org/dev/core/-/issues/4163
Before
FormBuilder tries and fails to autocomplete ParticipantStatusID
After
Since that entity hasn't (yet) been implemented in APIv4, it falls back to using the option list.
Technical Details
Since APIv4 getFields is specific to, well, APIv4, it probably shouldn't link to entities that don't exist in APIv4.