Skip to content

Update ID Extraction to account for new type expectations after flattening enhancement

Levi Remington requested to merge fix-id-flattening-lr into master

Type of change

  • Bug Fix
  • Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record) #470 (closed)

Does this introduce a change in the core logic?

  • [YES/NO]

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • AWS
  • Azure
  • GCP
  • IBM

Does this introduce a breaking change?

  • [YES/NO]

What is the current behavior?

  • Flattening logic converts all complex presentations into stringified forms of the original JSON
  • ID value is never in array form, always in string form
  • Spatialization logic anticipates ID value may be in Array form -> leads to conflict

What is the new/expected behavior?

  • Spatialization logic anticipates ID value to be in String form -> resolves conflict
  • If string represents stringified array, string is parsed back into array for Spatialization -> maintains special handling for multiple ID scenario

Merge request reports