Yannick Schinko

Since I'm not programming in Go that's not relevant for me.

This issue is still present. And essentially rendering this feature pretty useless. #692 seems to be related.

I don't think it makes sense throwing the auto remove groups after deletion here.

I still feel like the last two are best sloved by a flag (or a flag to not do it) and so I don't quite understand why they're being grouped...

I'll post it again: For rename: Have it bulkupdate by default and a flag to disable that behavior. So that the most common use case is the default.

I was implying that but that’s a fair point to point out.

I've had an idea on how this could be implemented and minimize impact when updating: Add a config setting that reenables the old (insane) behavior. In the default config it...

Bumping it because I've yet seen another case where this causes massive issues.

It's not just difficult to explain the why but it's even more difficult to suggest somewhat decent solutions. Even helper groups that inherit the actual group twice, once with the...

> Currently, the server context is a way of isolating permissions to a specific LP instance That is correct and that is *exactly* the issue here. Contexts are used to...