When I start typing in the middle of an existing line and accept an autocomplete suggestion, it deletes the rest of the text up to the next operator character.
No other IDE that I use does this. 100% of the time I don’t want it to do this.
Expected behavior
It should insert the autocompleted text, not replace it.
If I had wanted it to replace it, I would have selected the entire remaining text myself before I started to type over it.
The same behavior occurs for both.
I really hate that this happens. I always have to add an extra peridot to ensure that it doesn’t remove any existing text
Enter doesn’t, at least for me, while only Tab has the behavior of replacing the entire symbol that you described:
Thanks for the report! I filed a ticket in our internal database and we’ll follow up when we have an update for you.
Don’t know why, there’s no settings for this as far as I can see, there’s no shortcuts, etc. Tab has the same behavior. If this separation between keys is an intentional feature in Studio, the expected behavior should be the default for enter and it should never be disabled. 
Yeah, I checked for any settings as well, doesn’t seem to be any. I recall seeing this tidbit from an engineer replying to another bug report of something who, I think, was saying the same thing you are, but I looked through my browsing history and found a Feature Request for some customizability instead:
Doesn’t seem like a bug regardless
EDIT: Oh, that Feature Request literally links to the Bug Report I was referring to
It is a bug because it breaks the majority user expectation. Bugs can be part of the product design too as far as I’m concerned, it’s an error in what the correct behavior should be. I am coming from a background using Visual Studio and Rider. These are arguably the top 2 most common classes of IDE - VS & JetBrains.
@idevride, what were the IDEs you were transitioning users from? I don’t understand this reasoning. This current behavior is incredibly disruptive and is at odds with industry software, and has completely driven me from allowing autocomplete to work in this context at all.
Just coming in here to throw in my two cents - I think this is buggy behavior, too.
I made that post under the Studio Features section as a suggestion so that I didn’t ruffle any feathers for rehashing a bug that had been handled and decided on by the IDE team previously. I was err -ing on the side of caution.
This is still disruptive behavior that should be at least standardized. There should be no difference between using the Tab key vs. the Enter key.
Ah so thats why it was happening, i thought it was an issue because of my plugin so i decided to fix the weird logic myself 
I hope this gets fixed soon for the rest though, it was very annoying