[SLING-10084] Prevent the creation of configuration properties with duplicate keys

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Feature Model 1.2.18
• Fix Version/s: Feature Model 1.2.20
• Component/s: Feature Model
• Assignee: A. J. David Bosschaert
• Reporter: A. J. David Bosschaert
• Created: 21/Jan/21 14:18
• Updated: 08/Feb/21 17:32
• Resolved: 26/Jan/21 10:40

Description

Having 2 (or more) properties in a single configuration with the same key regardless of capitalization is an invalid situation and should not be allowed in feature models.

When reading or writing a feature we should fail if the feature is detected to have duplicate property keys within a single PID by comparing the keys in a case insensitive way.

Issue Links

• links to: GitHub Pull Request #23