Merged
Conversation
…eir direct ancestors in a way that no longer recreate the activity and all linkeages. Because the existing implementation involved using query functions that deleted everything, it became necessary to make new query functions to accommodate this change, and now we have a solution that handles each ancestory individual, either deleting or adding
…ect ancestors that caused activities to not be created on a POST
…how ancestors linked, unliked, or if there are none. Also rewrote link_sample_to_direct_ancestored to better handling ancestors as lists or strings
…now gracefully handles all incoming data as a list regardless if its only one value or not, and addresses earlier bugs
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Following merged PR #933 #924 #936 #940 for TEST