fix: passes draft=true in fetch for relationships
#4784
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
added 2 commits
January 11, 2024 14:59
PatrikKozak
requested review from
jmikrut,
jacobsfletch,
JarrodMFlesch,
denolfe and
DanRibbens
as code owners
PatrikKozak
changed the title
?draft=true to fetch for relationshipsdraft=true in fetch for relationships
DanRibbens
reviewed
Jan 12, 2024
added 2 commits
January 12, 2024 10:27
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.
Description
Fixes #2997
When fetching for a doc from a
relationshipfield, if the doc is adraftand has nopublishedversions - the relationship field dropdown would still find the doc but showUntitled - ID: 1234even if the doc had a title.This fix now fetches relations with
draft=truein order to correctly display the appropriate data.Type of change
Checklist: