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

Issue warning when undefined variables are accessed

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.4.0
    • Component/s: Compiler
    • Labels:
      None
    • Template:
    • Epic Link:
    • Story Points:
      1
    • Sprint:
      Language 2016-02-10, Language 2016-02-24
    • Release Notes:
      New Feature
    • Release Notes Summary:
      Hide
      All references to non existing variables will now generate a warning. Earlier puppet only warned about non existing qualified variables with more than one namespace segment.

      It is possible to disable these warnings by adding 'undefined_variables' to the setting 'disabled_warnings'.

      Note that in most cases there is no file/line information available, and this was one reason why only some cases were reported earlier. We expect to correct this in the next major version as it requires API breaking changes.
      Show
      All references to non existing variables will now generate a warning. Earlier puppet only warned about non existing qualified variables with more than one namespace segment. It is possible to disable these warnings by adding 'undefined_variables' to the setting 'disabled_warnings'. Note that in most cases there is no file/line information available, and this was one reason why only some cases were reported earlier. We expect to correct this in the next major version as it requires API breaking changes.

      Description

      We are going to turn the default to use strict variables after 4.x. We need to issue warnings when strict is not enabled.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  andy Andrew Parker
                  QA Contact:
                  Kurt Wall
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support