-
Notifications
You must be signed in to change notification settings - Fork 35
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
(MODULES-9370) Raise Supported Puppet lower bound from 4.9.0 to 5.5.10 #88
(MODULES-9370) Raise Supported Puppet lower bound from 4.9.0 to 5.5.10 #88
Conversation
| @@ -0,0 +1,6 @@ | |||
| { | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we tracking vscode recommendations per module?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is PDK-ified now?
| end | ||
|
|
||
| start_time_valid = time_valid?(manifest_hash['start_time']) | ||
| raise ArgumentError, "Invalid start_time value: #{manifest_hash['start_time']}" unless start_time_valid |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand why these errors don't need to be decorated like _("Invalid start_time value...")
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Line ending and question about decorator
This commit begins the alignment process of the module to the core structure, updating the project files and turning on rubocop. Importantly, in this first commit, the rubocop violations are not addressed but are instead recorded in a TODO. They will be addressed in future commits.
This commit enforces rubocop on the tests but *not* on the actual code. This is to ensure that tests continue to pass and we have confidence that the changes do not introduce any regressions.
This commit removes shebangs from the spec test files as these cause rubocop to mark the files as `should be executable` and fail if the file was saved on windows - during checkout, those files are not marked executable due to differences in the permissions models on windows/unix.

Building on the work by @florindragos in #86, this PR makes a few small changes to the actual files but largely just splits the commits to ensure only the tests or library code are being changed at a time to keep confidence that no regressions are introduced.