Skip to content

Conversation

@Thomas-Franklin
Copy link
Contributor

@Thomas-Franklin Thomas-Franklin commented Oct 25, 2018

If there is a top level module with same name as a type which gets loaded before the type gets defined then this will trigger a false positive on the last_module.const_defined? check causing an uninitialized constant error.

This change will no longer do a recursive check and only care about the local namespace this way avoiding the false positive.

If there is a top level module with same name as a type which gets loaded before the type gets defined then this will trigger a false positive on the last_module.const_defined? check causing an `uninitialized constant` error.

This change will no longer do a recursive check and only care about the local namespace this way avoiding the false positive.
@DavidS DavidS merged commit 5173d4a into puppetlabs:master Oct 25, 2018
@DavidS DavidS added the bug label Oct 25, 2018
DavidS added a commit to DavidS/puppet-resource_api that referenced this pull request Oct 25, 2018
Same as puppetlabs#132, there are more const_get and const_defined? calls that
need to ignore inherited names.
DavidS added a commit to DavidS/puppet-resource_api that referenced this pull request Oct 25, 2018
Same as puppetlabs#132, there are more const_get and const_defined? calls that
need to ignore inherited names.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants