Skip to content

Conversation

@gouttegd
Copy link
Contributor

If both the default module type and the module type for a specific import are set to slme, but the specific module has a slme_individuals setting that is different from the default (group-level) setting, then that module will require a specific rule to honor the module-level slme_individuals setting.

closes #1305

If both the default module type and the module type for a specific
import are set to `slme`, but the specific module has a
`slme_individuals` setting that is different from the default
(group-level) setting, then that module will require a specific rule to
honor the module-level `slme_individuals` setting.

closes #1305
@gouttegd gouttegd self-assigned this Nov 27, 2025
@gouttegd gouttegd requested a review from matentzn November 27, 2025 14:12
Copy link
Contributor

@matentzn matentzn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM but these conditions require a moment to mentally execute :)

@gouttegd
Copy link
Contributor Author

Hopefully the corresponding code in the new ODK Core project will be more easily readable. :)

@gouttegd gouttegd merged commit 164c1d8 into master Nov 27, 2025
1 check passed
@gouttegd gouttegd deleted the fix-ignored-slme_individuals-setting branch November 27, 2025 15:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

BUG: slme_individuals flag in config.yaml not used for building import modules

3 participants