APIv4 - Remove POC code leftover from early alpha development #20709
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
During early APIv4 development there was an idea to create a BridgeJoinable class and connect things like activity->assignees. It was experimentally implemented for that field one field, but never documented or tested.
|
(Standard links)
|
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
Removes some undocumented, untested POC code from APIv4.
Comments
During early APIv4 development there was an idea to create a
BridgeJoinableclass and connect things like activity->assignees.It was experimentally implemented for that field one field, but never documented or tested.
Note: This shouldn't be confused with the new
EntityBridgeAPIs which are well-tested and not going anywhere.