Currently when using a Computed Token Field, if any part of the "token value" of the field for a given entity doesn't render to an actual value, the token is left in place and ends up showing as part of the value of the computed field. This exposes implementation detail to the user and should not happen.
1. Configure a Computed Token Field, using a token that references an optional field on the same node type.
2. Create a node of the given node type, and leave the value of the optional field empty. Save the node.
3. Observe that the Computed Token Field is rendered with the [node:field_optional:value] or similar "token value" on the node view page.
Leverage the "clear" option on Token::replace to remove unrendered entities from the computed field value.
Patch the module.
Unrendered token values will no longer appear when rendering Computed Token Fields.
Active
1.0
Code
Issue #3512590: Clear non-rendered tokens from field value