[DELTASPIKE-1147] TypedResolver behaves different than ConfigResolver

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.6.1
• Fix Version/s: 1.7.0
• Component/s: Configuration
• Assignee: Mark Struberg
• Reporter: Mark Struberg
• Created: 17/May/16 15:59
• Updated: 19/Jun/16 23:09
• Resolved: 17/May/16 17:15

Description

We have some cases where the TypedResolver return different values than performing the same operation via the legacy ConfigResolver API.

1.) default values of 'null' get handled different
2.) ProjectStage specific empty values abort the resolver chain in older versions. In 1.6.1 it continues the evaluation. This leads to different values.