Can I use pseudofields in anything other than source?

Geat

5/16/24, 12:06 AM

If I use pseudofields in the source property for my custom plugin, they are correctly substituted with the computed values. If I use them in another configuration (as per the example), they are treated as literal strings:

 field_myfield:
    -
      plugin: my_custom_plugin
      items:
        -
          title: 'Title 1'
          content: '@computed_field_1'
        -
          title: 'Title 2'
          content: '@computed_field_2'

Is what I'm attempting actually possible?

0 + 0

migrations

configuration

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Can I use pseudofields in anything other than source?

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.