fails on duplicate description

[Boruch-Baum]

I intended to report an issue, but your project has taken the Quite unusual effort to configure github to nudge me here instead. Fine, I'll respect that, but please respect me enough not to expect me to do double work for you by ALSO submitting an issue after this.

ISSUE:
If you create a new snippet, but type in a comment that duplicates that of a prior snippet, the program exits with an error message "snippet [...] already exists" instead of prompting for a new comment.

VERSION: 1.0.1

ENVIRONMENT: debian/bash

[RamiAwar]

What do you mean by "comment"? @Boruch-Baum

[Boruch-Baum]

The user response to the program's prompt "description"

[RamiAwar]

So you're saying the current behavior of preventing duplicate snippet descriptions forces you to restart from the beginning and you would like it to re-prompt only the description instead?

[Boruch-Baum]

I don't tell volunteer FOSS developers what to do. I'm just reporting the issue. Apologies for not having a PR to offer.

[RamiAwar]

1- This isn't really an issue, it's more of a request for behavior change. (This is why I want people opening discussions, cause then I can identify whether or not something is a real issue. That's what discussions are for and many other repos use this too.)

2- I'm asking you about your experience, so that I can understand the difficulty here. I'm not asking you to 'tell me what to do'. I'm simply trying to understand my user here. So help me understand what the problem is. Is it what I described above?

3- I don't want a PR for this, I'm not even sure this is something we want to do yet, hence the discussion.

I have to say, your tone from the beginning of this discussion is not nice nor productive. No one asked you to 'contribute more of your time to opening an issue AS WELL', so why are you coming in with this uncalled-for negative attitude? And the description of the problem is not descriptive enough, and your response to my user experience question is totally irrelevant "I don't tell FOSS developers what to do" (????). Help me help you better, I don't need to be constantly asking followups and dealing with negativity. @Boruch-Baum