Skip to content

Conversation

jaeopt
Copy link
Contributor

@jaeopt jaeopt commented Feb 11, 2022

Summary

  • When an attribute value is missing, semantic-version matcher returns the "unexpected-value" error message as the WARNING level.
  • The same wrong error message is also given for exact matcher when the value is number type.
  • This is fixed to the "missing-attribute" message as the DEBUG level, to be consistent with other condition matchers.

Test plan

  • Unit tests for all matchers with missing attribute value.

Issues

@coveralls
Copy link

coveralls commented Feb 11, 2022

Pull Request Test Coverage Report for Build 1951

  • 7 of 7 (100.0%) changed or added relevant lines in 6 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.01%) to 90.752%

Totals Coverage Status
Change from base Build 1950: 0.01%
Covered Lines: 4877
Relevant Lines: 5374

💛 - Coveralls

@jaeopt jaeopt removed their assignment Feb 11, 2022
@jaeopt jaeopt changed the title fix(semantic-version): log debug instead of warning for missing attribute value fix(audience): log debug instead of warning for missing attribute value Feb 14, 2022
Copy link
Contributor

@msohailhussain msohailhussain left a comment

Choose a reason for hiding this comment

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

please update copyright

Copy link
Contributor

@msohailhussain msohailhussain left a comment

Choose a reason for hiding this comment

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

lgtm, please update copyright.

@jaeopt jaeopt merged commit d8df159 into master Feb 16, 2022
@jaeopt jaeopt deleted the jae/sem-warn branch February 16, 2022 01:09
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