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

Refactor validation of 4.x parameter signatures

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.3.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Story Points:
      3
    • Sprint:
      Language 2015-04-29, Language 2015-05-13, Language 2015-05-27, Language 2015-07-08, Language 2015-09-30, Language 2015-10-14
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      This makes the typechecking and reporting of parameter types consistent. Earlier there were several different implementatations and they differed in how they checked and reported type mismatches.

      Description

      The code that performs validation of parameters when calling functions, lambdas, or instantiating resource or class definitions resides in different places today and produces different error messages. This code should be refactored so that it handles all types of parameter validation.

      The code must be able to handle both pure indexed based parameter passing (functions and lambdas) and parameters passed by name (resource and class instantiations).

      QA


      risk: low (refactor)
      probability: medium
      severity: low
      testing layer: unit/acceptance (as-is)

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support