Skip to content

Conversation

@natemccurdy
Copy link

Noticed that the module had a low score on the Forge because of these style issues. This PR should help.

There's still one more issue affecting the score, and that's the unbounded dependency on puppetlabs/postgresql. I don't know enough about compatibility to put a limit on the version, so I let that one go.

},
false => "${::memory['system']['total_bytes'] / 1024 / 1024 / 3}MB",
true => "${::memory['system']['total_bytes'] / 1024 / 1024 / 8}MB",
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this really a readability win? I don't think I agree with puppet-lint on this warning

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm with you on that. I don't like this change and will put it back.


if ( versioncmp('2017.2.0', $facts['pe_server_version']) >= 0
and $manage_fact_values_autovacuum_cost_delay ) {
if (( versioncmp('2017.2.0', $facts['pe_server_version']) >= 0 ) and $manage_fact_values_autovacuum_cost_delay ) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also don't think this is a readability win either

pe_databases::set_puppetdb_table_autovacuum_cost_delay_zero { 'reports' : }
}
}

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

whitespace

Copy link
Author

@natemccurdy natemccurdy Aug 3, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

interesting. why does that matter? Is this some sort of text editor compatibility thing? Or just arbitrary?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not actually sure. But I've been putting a new line at the end of manifests ever since I saw that in the style guide.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suspect it's like all whitespace rules - there to prevent pointless problems with diffs on merges. It doesn't require an empty blank line, though - if the last line ends with a newline it should be ok, shouldn't it?


if ( versioncmp('2017.2.0', $facts['pe_server_version']) >= 0
and $manage_fact_values_autovacuum_cost_delay ) {
if ( versioncmp('2017.2.0', $facts['pe_server_version']) >= 0 )
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the complaint here?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think between commits you accidentally moved the paran

@npwalker
Copy link
Contributor

@natemccurdy looks like there's a conflict. If you can fix the paran and the merge conflict I'll look to merge this in.

@npwalker
Copy link
Contributor

Most of what this PR tried to change I changed when I made it compatible with PDK. However, I didn't realize you could do multiple line puppet lint ignores so I updated the PR to do that one thing.

@npwalker npwalker merged commit e6b3ff0 into puppetlabs:master May 23, 2018
@natemccurdy natemccurdy deleted the lint_fixes branch May 23, 2018 16:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants