SETATTRIBUTES strange behaviour

[miton18]

In WarpScript, it's possible to RELABEL a GTS with a NULL value, this action drop the label from the GTS.

It seems not possible to do the same thing with SETATTRIBUTES, is it an expected behaviour ?

Quantum example

[hbs]

Attributes are only set as a whole so yes this is the expected behavior

[miton18]

Sorry, don't understand... In a GTS instance, on an WarpScript context:

• to drop a label, I can use { 'attr' '' } RELABEL
• to drop an attribute, I can use { 'attr' '' } SETATTRIBUTES
• to drop a label, I can also use { 'attr' NULL } RELABEL
• to drop an attribute, I can't use { 'attr' NULL } SETATTRIBUTES

Even if the data structure for Attributes and Labels are differents, Why SETATTRIBUTES function cannot handle NULL value as empty string one ?

[hbs]

The NULL value was incorrectly rejected due to a misplaced check.

You should have received an exception saying arguments were not STRING.

Fixed now, thanks for the catch.

[miton18]

Thx @hbs :-)