APIv4 - Delete undocumented deprecated activityType lookup #20506
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)
|
|
Looks good to me |
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
Deletes an undocumented APIv4 quirk that's been giving deprecated warnings for over a year.
Before
When creating an Activity, APIv4 would accept
activity_typeas a string.This was never documented or available in the Api Explorer, and has been giving deprecated warnings since May 2020.
After
Quoth the raven, nevermore.
Technical Details
It was an early POC of a possible way to do option lookups from the pre-alpha APIv4 extension. Didn't catch on.