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

Distinguish different errors when relating an update channel to target groups #529

Open
davidebriani opened this issue May 27, 2024 · 0 comments
Open

Distinguish different errors when relating an update channel to target groups #529

davidebriani opened this issue May 27, 2024 · 0 comments
Labels
ash-porting Issues used to track open issues regarding the Ash porting process enhancement New feature or request

Comments

@davidebriani
Copy link
Collaborator

davidebriani commented May 27, 2024 •
edited
Loading

Currently, a single generic error is returned when an update channel cannot be correctly related to a list of target groups: for example if some target groups don't exist or are already related to an update channel.

A possible approach could be to use Ash.Expr as suggested here: #521 (comment)
@davidebriani davidebriani added enhancement New feature or request ash-porting Issues used to track open issues regarding the Ash porting process labels May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ash-porting Issues used to track open issues regarding the Ash porting process enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@davidebriani