fix: fixing countDraftRelations to get locale as a prop #20324
+6
−3
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
|
joshuaellis
added
source: core:content-manager
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.
What does it do?
Modified countDraftRelations to retrieve the locale from parameters, allowing it to verify the single type for the specified query locale instead of defaulting to the locale
Why is it needed?
Currently, countDraftRelations does not retrieve a specified locale. The locale is not provided in the parameters that's why the default locale is used to fetch the entity from the database. If the entity has not been created in the default locale, users will be unable to publish the single type in their specified locale.
How to test it?
Related issue(s)/PR(s)
This PR fixes this issue #20188