3

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?

1

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Browse other questions tagged or ask your own question.