I'm confused about the @ versus $ usage. I was under the impression that the new workflow would be that we use attributes with @ now, but I'm still relying on $ in a number of places.

The two places that I just randomly attempted to use @ were in the rule parameter on a partition node, and in a transform parameter on a primitive node. In both cases I fell back on $ instead of @ and then it worked fine.

Is there a logic to this mechanism that I'm missing? Is there some sort of a list anywhere on cases where we should expect to use one over the other? If we encounter a place where @ doesn't work should we be filing a bug?

Ah… I see on the primitive it still accepts $CLASS, but the usage should be @class not @CLASS. I was thrown off by the lack of an error.

But in the case of the partition node, it wanted `@class` rather than $CLASS. I guess that's to be expected in string workflow?