This repository has been archived by the owner on Aug 23, 2023. It is now read-only.
add values policy to mt-fakemetrics #1773
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
replay
reviewed
Apr 15, 2020
replay
reviewed
Apr 15, 2020
Dieterbe
reviewed
Apr 16, 2020
Dieterbe
reviewed
Apr 16, 2020
replay
approved these changes
Apr 16, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR adds a
value-policyoption tomt-fakemetrics. It is explained in greater detail in the tool'sREADMEfile.It adds 3 options initially:
If no policy is specified the default behavior of generating a random float is still used.