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

Theme: Modularity - improve Puppet's modularity

    Details

    • Type: Epic
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Epic Name:
      Theme: Modularity
    • Template:

      Description

      Update


      This Epic is repurposed to be the thematic epic "Theme: Modularity" which includes protecting private classes/types and parameters, dependencies between modules, and modularity in general.

      This epic used to be a very broad "quality, strictness and safety", but that is a scope that is too broad. Many of the tickets in this epic should be moved to the other themes, or epics for a specific release cycle. e.g. "4.x Modularity", "5.x Modularity", or "4.x Code Validation",

      Original


      The puppet language still has a lot of gotchas that can crop up. Many of these allow unexpected behavior to occur or get rid of the guarantees expected by users such as immutability, strictness about variable use, and difficulty creating good encapsulations. We need to implement something like a "strict mode" that lets users turn on certain checks in certain cases and in other cases we need to provide new functionality to let them express what is really needed.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                henrik.lindberg Henrik Lindberg
                QA Contact:
                Kurt Wall
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support