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

Error handling for duplicate Boefje name #3566

Closed
1 task
madelondohmen opened this issue Sep 19, 2024 · 0 comments · Fixed by #3573
Closed
1 task

Error handling for duplicate Boefje name #3566

madelondohmen opened this issue Sep 19, 2024 · 0 comments · Fixed by #3573
Assignees
Labels
boefjes Issues related to boefjes frontend

Comments

@madelondohmen
Copy link
Contributor

About this feature

Detailed description

Currently, there's no error handling in the frontend for creating a Boefje with an already existing name.

Feature benefit/User story

As a user, I want to get an error message when I create a Boefje with a name that's already in use, so that I understand what I did wrong while creating the Boefje.

Specifications

  • Error message

Additional information

Any additional information, considerations, or context that might be helpful for understanding or evaluating the feature request.

Design

This part should only be filled in by the OpenKAT design team.

Screenshots

Include screenshots of the proposed design changes here.

Figma link

Link to the Figma design for further visualization (if applicable)

Implementation

This part should only be filled in by the developers.

Possible solution

Outline your proposed solution for implementing the feature. You can include any specific ideas, designs, or functionalities here.

Alternatives considered

Describe any alternative approaches or solutions you've considered, and why you believe the proposed solution is superior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
boefjes Issues related to boefjes frontend
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants