Assignment Definition Changes

[01Parzival10]

Instead of using the WebEditor specific behavior definition, assignments are now defined like they are in the DFD-MetaModel.

Former set-Actions now work like this:
Assignment({input_Pins};Term;{out_Label}) e.g. Assignment({data, request};Sensitivity.Personal || TRUE;{Sensitivity.Public})

forwarding now like this:
Forwarding({input_pins})
e.g. Forwading({data|request, encrypt}) [with data|request being the pin where both data and request arrive]

Auto-Completion and validation have been adjusted

[uuqjz]

I have three suggestions for changing the regex, mainly disallowing whitespace for simplicity and some consistency for naming and using delimiters

[Nicolas-Boltz]

This regex requires a comment that really explains what it does

[uuqjz]

Maybe we could also use constants for the delimiters (,|) in case we ever change them

[01Parzival10]

Maybe we could also use constants for the delimiters (,|) in case we ever change them

Then you'll have to build the Regex from that
I think we should do it for the Pipe but I see no reason to change the comma as list separator

EDIT:
Or maybe leave it all together. Since pipes need to be escaped one would need to touch the Regex either way when they replace the delimiter

[01Parzival10]

This regex requires a comment that really explains what it does

Agreed. I added documentation

[uuqjz]

You still allow | pipes in labels...

[01Parzival10]

You still allow | pipes in labels...

Fixed that

[uuqjz]

LGTM

[uuqjz]

There are issues with your term validation
!Sensitivity.Pe..rs_ is marked as valid
! is marked as valid
These two i found by trying there might be more

[01Parzival10]

There are issues with your term validation
!Sensitivity.Pe..rs_ is marked as valid
! is marked as valid

The same issue existed beforehand. I just adjusted the Editor to the new logic there

[01Parzival10]

There are issues with your term validation
!Sensitivity.Pe..rs_ is marked as valid
! is marked as valid

The same issue existed beforehand. I just adjusted the Editor to the new logic there

At least the ! Issue. I'll take care of the label issue

[01Parzival10]

There are issues with your term validation
!Sensitivity.Pe..rs_ is marked as valid
! is marked as valid

The same issue existed beforehand. I just adjusted the Editor to the new logic there

At least the ! Issue. I'll take care of the label issue

Done @uuqjz

[uuqjz]

Sensitivity.Personal. is marked as valid
Sensitivity.Personal.ABC. is too

[01Parzival10]

@uuqjz I fixed that but Validation and Suggestions need to be touched by our new WebDev anyway. This code is hotglued together to work

[uuqjz]

@Nicolas-Boltz please rereview. Its fine (for now) from my side.
@Kr0nox will at some point have to refactor this.

[Nicolas-Boltz]

Looks good to me
@01Parzival10 I leave it up to you to merge this.