dprakash2101 Shared-code impact
Before editing shared code:
- Search all usages, registrations, implementations, overrides, tests, serialization points, and externally exposed consumers that are reasonably discoverable.
- Identify existing behavior each consumer may rely on, including legacy, customer, reseller, region, integration, sender, flag, and workflow variants.
- Decide whether the requirement is truly global. If not, prefer a scoped branch, strategy, adapter, overload, configuration, or caller-specific transformation consistent with the codebase.
- Preserve defaults and compatibility. Avoid silently broadening validation, mapping, logging, retries, or exception behavior.
- Test the changed scenario and representative unaffected consumers, especially default behavior.
Existing unusual or duplicated code is not permission to clean it up. If impact cannot be bounded with available evidence, state the uncertainty before making a high-blast-radius change.