Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Author field perhaps is null #15457

Merged
merged 1 commit into from
Mar 7, 2024
Merged

Author field perhaps is null #15457

merged 1 commit into from
Mar 7, 2024

Conversation

hyzx86
Copy link
Contributor

@hyzx86 hyzx86 commented Mar 5, 2024

No description provided.

Copy link
Member

@MikeAlhayek MikeAlhayek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think even Owner can be nullable if the user provider no id during a recipe import.

@hyzx86
Copy link
Contributor Author

hyzx86 commented Mar 7, 2024

Hi @Skrypt , what do you think ? I remember you seem to have related PR, about index table fields.

@MikeAlhayek MikeAlhayek merged commit 0c313ab into OrchardCMS:main Mar 7, 2024
4 checks passed
@hyzx86
Copy link
Contributor Author

hyzx86 commented Mar 9, 2024

I think even Owner can be nullable if the user provider no id during a recipe import.

Yes indeed ,There are some situations in my content items where the owner is empty, such as content items created by workflow or background threads. In order to prevent graphql from making errors, I can only exclude this field. In fact, rendering this field in graphql has no practical meaning. Unless the user wishes to send further requests through graphql's request results

@hyzx86
Copy link
Contributor Author

hyzx86 commented Mar 9, 2024

@MikeAlhayek , I pushed a new PR #15477

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants