Sayt Configuration & Code Generation FAQs

Question 1

What file formats does Sayt support for configuration?

Accepted Answer

Sayt finds and merges files matching .say.cue, .say.yaml, .say.toml, .say.json, and .say.nu into a unified configuration for generation and linting.

Question 2

What is the benefit of using .say.nu files?

Accepted Answer

.say.nu files allow for dynamic configuration. They are executed as Nushell scripts, and their output is piped into the CUE evaluation process, enabling runtime logic in your config.

Question 3

What is the difference between 'sayt generate' and 'sayt lint'?

Accepted Answer

While both use the same rule structure, 'generate' rules are intended to produce output files (like code or manifests), whereas 'lint' rules are for verification and must not produce output files.

Question 4

How do I force file overwrites during code generation?

Accepted Answer

By using the --force flag with 'sayt generate', which sets an environment variable that your Nushell command blocks can check to enable force-saving of files.

Question 5

How does the 'ordered map' pattern work in Sayt rules?

Accepted Answer

It uses keys to allow granular modification. You can add new rules with unique keys, modify existing ones by referencing their keys, or delete built-in rules by setting their key to null.

Sayt Configuration & Code Generation

주요 기능

사용 사례

Sayt Configuration & Code Generation

주요 기능

사용 사례