Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Grandchild module orphans should be destroyed #2786

Merged
merged 5 commits into from
Jul 20, 2015

Commits on Jul 19, 2015

  1. Configuration menu
    Copy the full SHA
    96a04c1 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    61d275f View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    edd05f2 View commit details
    Browse the repository at this point in the history

Commits on Jul 20, 2015

  1. core: add failing deeply nested orphan module test

    I was worried about the implications of deeply nested orphaned modules
    in the parent commit, so I added a test. It's failing but not quite like
    I expected it to. Perhaps I've uncovered an unrelated bug here?
    
    /cc @mitchellh
    phinze committed Jul 20, 2015
    Configuration menu
    Copy the full SHA
    392f561 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    955bbbb View commit details
    Browse the repository at this point in the history