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

Discriminate non-existing components and not processed components in error messages #3

Open
fuersten opened this issue Nov 14, 2022 · 0 comments
Open

Discriminate non-existing components and not processed components in error messages #3

fuersten opened this issue Nov 14, 2022 · 0 comments
Assignees
@fuersten
Labels
bug Something isn't working

Comments

@fuersten
Copy link
Contributor

fuersten commented Nov 14, 2022 •
edited
Loading

If a component was not processed due to errors (e.g. component type not ok) and is not available for relation references, the error message should reflect that. Currently, the error message will specify, that the component does not exist, which is not right.
@fuersten fuersten added bug Something isn't working and removed enhancement New feature or request labels Feb 9, 2023
@fuersten fuersten added this to the Version 1.1 milestone Feb 10, 2023
@fuersten fuersten removed this from the Version 1.1 milestone May 26, 2023
@fuersten fuersten self-assigned this Jun 28, 2023
@fuersten fuersten modified the milestone: Version 1.2 Mar 11, 2024
@fuersten fuersten removed this from the Version 2.0 milestone Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fuersten fuersten

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fuersten