Consistently use "dynamic type name" and "expression" instead of "variable value" in TypedConfigManager's terminology

Use the term dynamic type names, which #2392057: Config schema fails to expand dynamic top-level types → introduced for TypedConfigManager::getDefinitionWithReplacements()'s

   * @param array $replacements
   *   An array of replacements for dynamic type names.

.

Related: 📌 [PP-1] Validate inputs of config schema's TypeResolver: only allow %parent, %type and %key Postponed .

Better title.

I agree that dynamic type expression is clearer than variable value. I think this is a good improvement.

I like "dynamic type name" as a consistent term. I am, however, okay with "dynamic type expression", although I think we would definitely want to provide a clear example of what one looks like, since it's a more generic/CompSci-ish term overall.

So:

• "Dynamic type name" is my first choice.
• "Dynamic type expression" is my second choice, as long as we are very clear, with examples, that this means "a type name which is dynamic and contains [ and ]".

Couple minor suggestions but this is light-years better than what's in HEAD. As far as I'm concerned, RTBC once my points are resolved. :)

Done!

Send it forth!

I was not bothered too much about the old name, but I agree that this is an improvement.

RTBC +1

Let's preserve BC and add replaceName/Variable back it but trigger deprecations.

• Change record created (was also missing! 🙈): https://www.drupal.org/node/3408266 →
• #13 addressed

Self re-RTBC'ing because this is such a trivial change.

Committed 2dc7b23 and pushed to 11.x. Thanks!

Automatically closed - issue fixed for 2 weeks with no activity.