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

(gh-cat-9) Add specific data types #181

Merged
merged 2 commits into from
Jun 24, 2022
Merged

(gh-cat-9) Add specific data types #181

merged 2 commits into from
Jun 24, 2022

Conversation

LukasAud
Copy link
Contributor

Previous to this commit, the wsus_client module would fail to start
unit and/or spec testing on any PR, crashing at the beginning of the
process and throwing syntax errors.

This commit aims to review and fix multiple syntax warnings, making sure
that the module complies with syntax standards and that each parameter
has an appropriate data type assigned.

Note: This is backwards incompatible.

@puppet-community-rangefinder
Copy link

wsus_client is a class

that may have no external impact to Forge modules.

wsus_client::setting is a type

that may have no external impact to Forge modules.

This module is declared in 1 of 579 indexed public Puppetfiles.


These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

Previous to this commit, the wsus_client module would fail to start
unit and/or spec testing on any PR, crashing at the beginning of the
process and throwing syntax errors.

This commit aims to review and fix multiple syntax warnings, making sure
that the module complies with syntax standards and that each parameter
has an appropriate data type assigned.

Note: This is backwards incompatible.
Prior to this commit, a different commit containing some syntax update
was implemented. However, this update broke several test cases.

This commit aims to update the unit_spec.rb test file so that its test
cases keep working as intended. It also makes a few changes on top of
the previous syntax update to help the test file run correctly.
Copy link
Member

@david22swan david22swan left a comment

Choose a reason for hiding this comment

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

LGTM

@chelnak chelnak merged commit 54f91f0 into main Jun 24, 2022
@chelnak chelnak deleted the syntax-fix branch June 24, 2022 09:38
jordanbreen28 added a commit that referenced this pull request Dec 13, 2022
Prior to this commit, spec tests for this module were not as strict on
error messages as was hoped due to changes introduced in
#181.

This commit aims to reduce the chance of erroneous tests appearing as
passed, by matching to more accurate and strict error messages.
jordanbreen28 added a commit that referenced this pull request Dec 13, 2022
Prior to this commit, spec tests for this module were not as strict on
error messages as was hoped due to changes introduced in
#181.

This commit aims to reduce the chance of erroneous tests appearing as
passed, by matching to more accurate and strict error messages.
jordanbreen28 added a commit that referenced this pull request Dec 13, 2022
Prior to this commit, spec tests for this module were not as strict on
error messages as was hoped due to changes introduced in
#181.

This commit aims to reduce the chance of erroneous tests appearing as
passed, by matching to more accurate and strict error messages.
jordanbreen28 added a commit that referenced this pull request Dec 13, 2022
Prior to this commit, spec tests for this module were not as strict on
error messages as was hoped due to changes introduced in
#181.

This commit aims to reduce the chance of erroneous tests appearing as
passed, by matching to more accurate and strict error messages.
jordanbreen28 added a commit that referenced this pull request Dec 14, 2022
Prior to this commit, spec tests for this module were not as strict on
error messages as was hoped due to changes introduced in
#181.

This commit aims to reduce the chance of erroneous tests appearing as
passed, by matching to more accurate and strict error messages.
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.

3 participants