Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
Project file masks three elements for screenshots. Staging has a clock widget that also needs masking, so I added it to envs/staging.yaml:
screenshots:
mask: ['[data-test="live-clock"]']Now the three from the project file are not masked any more and every visual baseline is failing on the cart badge. I expected the lists to be added together.
Accepted answer
Arrays replace. Objects merge recursively, arrays are treated as one value and the later layer wins outright.
So write the whole list:
screenshots:
mask:
- '[data-test="shopping-cart-badge"]'
- '[data-test="live-clock"]'It reads as duplication and it is, but the alternative is worse: if arrays concatenated there would be no way to remove an entry from a lower layer, and every list in the tree would grow monotonically as you added environments.
Same rule, three more places it catches people:
heal.actions — patch it in an env file with [click] and fill, select, assert and the rest stop healing.--process pr-check, whose browsers: [chromium] replaces the project list of chromium, firefox and webkit. That one is intentional but it surprises everybody the first time a PR run only covers one browser.-b, which build a list and then replace the project list rather than narrowing it.A whole array is one row in the provenance table, so this is visible directly:
sdods config show -p demo-shop -e staging --explainIf project.screenshots.mask says envYaml, the env file owns the entire list and the project file contributed nothing to it.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.