paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 36 Packages Projects Releases Wiki Activity

chore: update formatting

Browse Source 
Signed-off-by: blam <ben@blam.sh>
This commit is contained in:
blam
2024-03-28 17:49:20 +01:00
parent 8f6356169c
commit 79b001fa7e
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
beps/NNNN-scaffolder-templating-in-parameters/README.md
+5 -5
View File
@@ -74,11 +74,11 @@ Inclusive of the initial RFC there's been a swarm of issues that are requesting
See the following:
- https://github.com/backstage/backstage/issues/16275
- https://github.com/backstage/backstage/pull/23283
- https://github.com/backstage/backstage/issues/19597
- https://github.com/backstage/backstage/issues/20533
- https://github.com/backstage/backstage/pull/17746
- [ ] https://github.com/backstage/backstage/issues/16275
- [ ] https://github.com/backstage/backstage/pull/23283
- [ ] https://github.com/backstage/backstage/issues/19597
- [ ] https://github.com/backstage/backstage/issues/20533
- [ ] https://github.com/backstage/backstage/pull/17746
There's some ideas for introducing a templating syntax for both templating into the `parameters` schema, and also being able to pass through some templating strings to underlying field extensions that can use those templating strings.
We want to align here so that we're not going to have those conflict or compete, and create a standard for how to achieve templating in both circumstances.