Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-7862

Optional types are not assignable to Data and RichData

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 5.2.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Sub-team:
    • Team:
      Platform Core
    • Story Points:
      1
    • Method Found:
      Manual Test
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      A regression was found in what a {{Data}} data type matches. Before the regression occurred this data type was too permissive in that it matched data that cannot be represented in JSON. After the regression the rules for matching became too strict for {{Undef}} values, and advanced matching between data types (instead of values) would also not match compliant {{NotUndef}} and {{Variant}} types.
      Show
      A regression was found in what a {{Data}} data type matches. Before the regression occurred this data type was too permissive in that it matched data that cannot be represented in JSON. After the regression the rules for matching became too strict for {{Undef}} values, and advanced matching between data types (instead of values) would also not match compliant {{NotUndef}} and {{Variant}} types.
    • QA Risk Assessment:
      No Action

      Description

      The implementation assumes that all values assignable to ScalarData also inherits from ScalarData. This means that an Optional, NotUndef, or Variant type that is limited to contain ScalarData types still isn't assignable to ScalarData.

      The same problem applies to Scalar.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              thomas.hallgren Thomas Hallgren
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support