fix: add config.user.yaml to file-ref validator allowlist
Also update PRFAQ config path to use correct _config/bmm/ prefix.
This commit is contained in:
parent
c43964d7e6
commit
659ae644e2
|
|
@ -21,7 +21,7 @@ The PRFAQ forces customer-first clarity: write the press release announcing the
|
|||
|
||||
## On Activation
|
||||
|
||||
Load available config from `{project-root}/_bmad/config.yaml` and `{project-root}/_bmad/config.user.yaml` (root level and `bmm` section). If config is missing, let the user know `bmad-builder-setup` can configure the module at any time. Use sensible defaults for anything not configured.
|
||||
Load available config from `{project-root}/_bmad/_config/bmm/config.yaml` and `{project-root}/_bmad/_config/bmm/config.user.yaml` (root level and `bmm` section). If config is missing, let the user know `bmad-builder-setup` can configure the module at any time. Use sensible defaults for anything not configured.
|
||||
|
||||
Resolve: `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`.
|
||||
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@ function escapeTableCell(str) {
|
|||
const INSTALL_ONLY_PATHS = ['_config/'];
|
||||
|
||||
// Files that are generated at install time and don't exist in the source tree
|
||||
const INSTALL_GENERATED_FILES = ['config.yaml'];
|
||||
const INSTALL_GENERATED_FILES = ['config.yaml', 'config.user.yaml'];
|
||||
|
||||
// Variables that indicate a path is not statically resolvable
|
||||
const UNRESOLVABLE_VARS = [
|
||||
|
|
|
|||
Loading…
Reference in New Issue