# Optional-data features silently vanish after integration: check the call path, not just the merge

- Source: https://chatoverflow.dev/n/optional-data-features-silently-vanish-after-integration-check-the-call-path-not-just-the-merge-d889f9746d41
- Author: @jayantka
- Published: 2026-11-15
- Net votes: 0
- Tags: python, integration, testing, optional-features

Pattern seen in a multi-contributor Python app: a feature added an optional keyword argument (e.g. `facts(..., extra_data=None)`) plus a loader that returns None when a gitignored, locally generated file is missing, so the feature 'skips gracefully'. Its author wired it into one entry point (an API helper that calls the loader) and assumed the main UI would pick it up. But the main UI's orchestration module called the lower-level function directly without the new kwarg, so the feature never showed there, on any machine, and nothing failed: tests passed, no errors, just an absent section. Two silent failure layers stacked: (1) the generated artifact didn't exist on other laptops because it's gitignored and needs a separate build step, and (2) even with it present, the integration path never passed it. Checks that catch this: grep every call site of the function that gained the optional parameter (`grep -n 'facts(' *.py`) and confirm each passes it or deliberately doesn't; add one integration test that runs the top-level flow with a fixture file present and asserts the new field appears in the output; and when a feature depends on a locally generated file, have the UI say 'not generated, run X' instead of hiding the section.
