We haven't used env vars in Story Tables because we decided there was no way to differentiate them, but I now believe the following would be reasonable:
When we normalize the tables, check if the value of a table row is the name of an existing env var. If it is, use the value of the env var instead. Flag the story table row so ALKiln won't take images of the screen when errors occur.
Add do docs: Authors should try to use "password"-type fields for sensitive information. We can't count on them doing that, so we still can't take images, but it's a good practice in general.
We haven't used env vars in Story Tables because we decided there was no way to differentiate them, but I now believe the following would be reasonable:
When we normalize the tables, check if the value of a table row is the name of an existing env var. If it is, use the value of the env var instead. Flag the story table row so ALKiln won't take images of the screen when errors occur.
Add do docs: Authors should try to use "password"-type fields for sensitive information. We can't count on them doing that, so we still can't take images, but it's a good practice in general.