Best ways to create a 1:1 relationship between a set of queries and some other settings?

EvanReese

I'm working on a feature that generates a list of parts, which should have some values associated with them by the feature. Later (in the same feature), when I query one of those parts, I want to be able to get a list of the settings for it. I thought I might be able to use the query itself as the key to a map, which would have all of the settings in it, but that didn't seem to work. I think I could use attributes, but I don't need to access this info in a downstream feature, so it doesn't feel quite right. Maybe that doesn't matter though. Any ideas on how to approach this?

ilya_baran

Attributes sounds right -- it doesn't matter if it's the same feature.  If you like, you can clear them at the end of your feature.

ilya_baran

Attributes sounds right -- it doesn't matter if it's the same feature.  If you like, you can clear them at the end of your feature.

EvanReese

Great, I'll go that route. thanks!

Konst_Sh

The transient query of the part should be pretty persistent in the scope of the feature as long as you don't use some non trivial body identity changing operations. Also if you decide to go with named attribute you can remove it in the end of feature by setting it to `undefined`