I hope thats everything

If you look at #193 we wanted to use a pipe as delimiter

I don't quite understand your regex changes. You put ;behind some _but not all. Additionally, shouldn't the new delimiter replace the old one?

I don't quite understand your regex changes. You put ;behind some _but not all. Additionally, shouldn't the new delimiter replace the old one?

You do want flow names to be allowed to have "_" in them, right?
| are only allowed in flow names, so in the latter part of the Regex

I don't quite understand your regex changes. You put ;behind some _but not all. Additionally, shouldn't the new delimiter replace the old one?

You do want flow names to be allowed to have "_" in them, right? | are only allowed in flow names, so in the latter part of the Regex

You mean | should only be allowed between flow names, right?

I don't quite understand your regex changes. You put ;behind some _but not all. Additionally, shouldn't the new delimiter replace the old one?

You do want flow names to be allowed to have "_" in them, right? | are only allowed in flow names, so in the latter part of the Regex

You mean | should only be allowed between flow names, right?

Yes.

But you do want "_" to be allowed in a single flow name and also in labels to be compatible with MicroSecEnd? That's why I didn't remove it from the Regex

But you do want "_" to be allowed in a single flow name and also in labels to be compatible with MicroSecEnd? That's why I didn't remove it from the Regex

Yes id like that

But you do want "_" to be allowed in a single flow name and also in labels to be compatible with MicroSecEnd? That's why I didn't remove it from the Regex

Yes id like that

Alright, it should be ready to merge then.

But you do want "_" to be allowed in a single flow name and also in labels to be compatible with MicroSecEnd? That's why I didn't remove it from the Regex

Yes id like that

Alright, it should be ready to merge then.

I will test the regex some more tomorrow then merge if i don't find an edgecase