Additional Tests to reinforce API filtering for Preprints [OSF-7418] #6828
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.
Purpose
There was some question previously about being able to get all "types" of preprints using the API preprint filter.
The general understanding was that Preprints can be in a few states (from the linked Jira ticket)
2, 3, and 4 should be included when ?filter[preprint]=false, 1 for true
This PR adds a few tests that better ensure that these conditions are met, specifically for double checking orphaned and abandoned preprints
Changes
filter[preprint]=False
and NOT infilter[preprint]=True
filter[preprint]=False
and NOT infilter[preprint]=True
Side effects
None
Notes!
I think some of the confusion on the Jira ticket revolved around API behavior when the
PreprintService
is deleted, what happens to theNode
that corresponds? I do believe this ticket in general was for the preprint filter, in the above states, and not withNode
-PreprintService
object relationships.Ticket
https://openscience.atlassian.net/browse/OSF-7418