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

Introduce ObjectDoesNotExist as OperationMessage.kind enum value #649

Open
1 of 3 tasks
tokr-bit opened this issue Oct 24, 2024 · 0 comments
Open
1 of 3 tasks

Introduce ObjectDoesNotExist as OperationMessage.kind enum value #649

tokr-bit opened this issue Oct 24, 2024 · 0 comments

Comments

@tokr-bit
Copy link
Contributor

tokr-bit commented Oct 24, 2024

I propose to introduce a new OperationMessage.kind value: ObjectDoesNotExist.

Feature Request Type

  • Core functionality
  • Alteration (enhancement/optimization) of existing feature(s)
  • New behavior

Description

If an object does not exist, Django raises an ObjectDoesNotExist-exception. This is translated into an OperationMessage with the kind field being set to OperationMessage.Kind.ERROR:

kind = OperationMessage.Kind.ERROR

However, as an API user, this value might be misleading. Therefore, I propose to introduce a new enum-Value, e.g. ObjectDoesNotExist.

Upvote & Fund

  • We're using Polar.sh so you can upvote and help fund this issue.
  • We receive the funding once the issue is completed & confirmed by you.
  • Thank you in advance for helping prioritize & fund our backlog.
Fund with Polar
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant