From e593d121a12ae477a3024a81dc123b5e3b85f079 Mon Sep 17 00:00:00 2001 From: blam Date: Thu, 25 Jul 2024 08:53:24 +0200 Subject: [PATCH] chore: update bep Signed-off-by: blam --- .../README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename beps/{0009-scaffolder-templating-in-parameters => 0010-scaffolder-templating-in-parameters}/README.md (94%) diff --git a/beps/0009-scaffolder-templating-in-parameters/README.md b/beps/0010-scaffolder-templating-in-parameters/README.md similarity index 94% rename from beps/0009-scaffolder-templating-in-parameters/README.md rename to beps/0010-scaffolder-templating-in-parameters/README.md index d5fc78497c..8d7a7b75d9 100644 --- a/beps/0009-scaffolder-templating-in-parameters/README.md +++ b/beps/0010-scaffolder-templating-in-parameters/README.md @@ -167,7 +167,7 @@ This is a pretty ugly workaround, but maybe the only option we have. Also at thi Perhaps we just accept this as a limitation, and document it as such. -Templating for `errorMessages` has been solved by using the `ajv-errors` library https://github.com/backstage/backstage/pull/25624, you can see more about [backrefs and pointers here](https://ajv.js.org/packages/ajv-errors.html). Any other template strings that will be passed through the underlying components and to be left untemplated should be encapsulated with options instead of passing through raw strings. The below example illustrates an `entityAndName` format, which under the hood, might do something like `${{ parameters.entity }} - ${{ parameters.name }}`, but this implementation never leaks out to the templating language. +Templating for `errorMessages` has been solved by using the `ajv-errors` library https://github.com/backstage/backstage/pull/25624, you can see more about [`backrefs` and pointers here](https://ajv.js.org/packages/ajv-errors.html). Any other template strings that will be passed through the underlying components and to be left untemplated should be encapsulated with options instead of passing through raw strings. The below example illustrates an `entityAndName` format, which under the hood, might do something like `${{ parameters.entity }} - ${{ parameters.name }}`, but this implementation never leaks out to the templating language. ```yaml parameters: