Closed elken closed 5 months ago
Hi 👋. Thank you for submitting your first issue to Homarr. Please ensure that you've provided all nessesary information. You can use the three dots > Edit button to update your post with additional images and information. Depending on the current volume of requests, the team should get in conact with you shortly.
Environment
NodeJS
Version
0.14.6
Describe the problem
As per title really, hit this when running locally adding another integration and have verified on my deployed version.
Looks like the config mutation just applies the new config regardless of what was there before, should be simple enough to check for collisions or just add some validation to the name field to protect against existing boards.
Logs
Nothing logged, this "seems" intended (though it's clearly not :) )
Context
All the action goes down in here
Please tick the boxes