All Submissions:

• Contributions should target the dev branch. Did you create your branch from dev?
• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren’t other open Pull Requests for the same update/change? ^Competing Bounty

New Feature Submissions:

1. Does your submission pass tests?
2. Have you formatted your code locally using cargo +nightly fmt --all command prior to submission?
3. Have you checked your code using cargo clippy --all --all-features command?

Changes to Core Features:

• Have you added an explanation of what your changes do and why you’d like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran tests with your changes locally?

/claim #3531

This is done via metadata forwarding when deserializing RangeInterface, and using a macro to define Condition that allows the separation of fields requiring custom deserialization from those that were fine with Derive from serde. I opted for a definition macro rather than a separate enum def in the function locally, to avoid the need for maintainers to duplicate field declarations. The macro setup will handle all required separation on its own, without the need to cross-check field declarations.