-
Notifications
You must be signed in to change notification settings - Fork 22
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
docs: setting horizon via configuration #221
Comments
Sorry for the confusion. The CLI flag is The |
Improved the README: - Added a table of contents. - New introduction example that shows comparing two benchmarks, instead of just one. - Consolidated and moved around a few sections. - Generally improved/made more concise some of the wording. - Fixed one or two errors/typos. - Fixed the test status badge. Also threw this in: - Separate `unit` vs `e2e` tests in `package.json`. Fixes #221 Fixes #223
I never liked the name "horizons" (except on the day I chose it I guess). I think a much clearer name is "auto sample conditions". This changes the `--horizon` flag and the `horizons` JSON config setting (yes... one was singular, the other plural) to `--auto-sample-conditions` and `autoSampleConditions` respectively. It's backwards compatible, with a warning printed if you use the old style. Related to #221
|
If setting
horizon
in configuration, it says this is not allowed. If providing--horizon
along with--config
it again says this is not allowed.The docs for the configuration instead use
"autoSampleConditions"
which is not documented and I wasn't able to locate this in the source code either.The text was updated successfully, but these errors were encountered: