Understanding 'memory' (storageType) in storageType^storagePath#property

[dmantisk]

I'll explain my confusion using the following examples all of which creates a simple list with selection

Example 1

INPUT[select(
option(option a),
option(option b)
)]

This does NOT store the selection anywhere; It works exactly as expected

Example 2

INPUT[select(
option(option a),
option(option b)
):memory]

This creates a property named 'memory' and stores the data in that; I expected it to not create any properties, but temporarily store the data in the file (I don't know where exactly)

Example 3

INPUT[select(
option(option a),
option(option b)
):memory^gibberish]

This temporarily stores the data somewhere WITHOUT creating a property. I added 'gibberish' because what I type there doesn't seem to matter; This is the behaviour I expected from example 2.

Question

Is this how it's supposed to work?

And if so where exactly is the temporary data stored for example 3? I want to be sure that the data is only temporary and doesn't end up accumulating somewhere

[mProjectsCode]

Yes, this is as expected. This docs page tries to explain it. In your second example, you only specify a property, so the storage type defaults to frontmatter.

The memory storage type stores the values in memory, meaning they do not persist anywhere.

[mProjectsCode]

The reason you need the "gibberish" property is so that you can have multiple independent memory properties in the same file and you can use the property to reference it elsewhere. E.g. a VIEW[{memory^gibberish}].

[dmantisk]

Thank you.
It being needed as an ID cleared my confusion.

Related to that, is it possible to set up if conditions for attributes like class? (Without js)
For example, have a VIEW field use one or the other class depending on the data in memory?
(Should I make a new post for this?)

[mProjectsCode]

If you mean CSS classes, then no, not without JS.

[dmantisk]

That's disheartening, but thank you