Thanks for the issue! PRs welcome to add the optionality.

How do you feel about removing it and pushing v3.0.0 with it? I think the proper fix is to remove it instead of working around the issue with an option.

We’d like to retain the behaviour so if you think it’s undesirable for your usecase, then we can make it an option (eg a suffix attribute which defaults to a space)

My use case might be something for GitHub to consider too:

• On a @ mention, the space is desirable as one usually starts a sentence.
• On a : emoji, the space is undesirable as it's often used to end a sentence.

A HTML attribute will not work as I need different behaviour per-key, so it needs to be an option that is set before event.detail.value is assigned. I'm thinking about event.detail.options as a options object with default value {suffix: ' '}.

Actually, a HTML option will work as well when set to the empty string as the optional space can be appended during the event.detail.value assignment based on key, so I'll go for that.