Add environment variable support to EditableTables #10143
-
In the spirit of #10111 - it would be great if we could use the autosuggested environment variables and aliases within an editable table field. There's already a "template" column type, so it should be a small change. My use-case is that I have a plugin that connects to an external API that can have multiple nodes for redundancy, and ideally a user should be able to use environment variables here. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Just added this for the next release (bf8b0a6). There’s a new {{ forms.ediatbleTableField({
staticRows: true,
cols: {
secretKey: {
type: 'autosuggest',
heading: 'Secret key'|t('plugin-handle'),
suggestEnvVars: true,
},
},
}) }} Also added support for Note that for both of these column types, autosuggestions will only work for rows that were included on the initial page load. So best reserved for editable tables where |
Beta Was this translation helpful? Give feedback.
Just added this for the next release (bf8b0a6).
There’s a new
autosuggest
column type which supports settingsuggestEnvVars
andsuggestAliases
keys totrue
on the column definition:Also added support for
suggestEnvVars
+suggestAliases
to thetemplate
column type.Note that for both of these column types, autosuggestions will only work for rows that were included on the initial page load. So best reserved for editable tables where
staticRows
is set totrue
.