Correct frequency offset in rules #145
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SitoRBJ
approved these changes
Jun 28, 2018
There was a problem hiding this comment.
Hello Team,
We have tested most of the rules that include the "frequency" field. In all of them, their activation is correct.
This PR depends on PR #827. Do not merge until both are ready.
Great job chemamartinez.
Kind regards,
Alfonso Ruiz-Bravo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to the PR: #827
It has been removed the +2 offset of the frequency option. This PR adapts existing rules frequency to the new equivalent values.