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.

Sign up for GitHub

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

Jump to bottom

DestinationSelectionLog model should require destination_id for most events #170

Open
scy opened this issue Oct 6, 2023 · 0 comments
Open

DestinationSelectionLog model should require destination_id for most events #170

scy opened this issue Oct 6, 2023 · 0 comments
Labels
area:backend Related to the server component prio:C Nice to have, but optional type:enhancement New feature or request

Comments

@scy
Copy link
Collaborator

scy commented Oct 6, 2023

Just as an additional guarantee, for all events that are associated with a Destination (i.e. most of them), the model should require destination_id to be set.
@scy scy added type:enhancement New feature or request area:backend Related to the server component labels Oct 6, 2023
@scy scy added this to the 2.0: instant call support milestone Oct 6, 2023
@scy scy changed the title DestinationSelectionLog model should require destination_id for most event DestinationSelectionLog model should require destination_id for most events Oct 6, 2023
@scy scy added the prio:C Nice to have, but optional label Oct 11, 2023
@scy scy removed this from the 2.0: instant call support milestone Dec 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area:backend Related to the server component prio:C Nice to have, but optional type:enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@scy