Skip to content

Ranges for macrotargets incorrectly documented as inclusive #424

Description

@Shatur

Documentation says:

- `lowest` (float) — Lower bound of this segment (inclusive). Slightly below 0.0 (e.g. `-0.01`) at the start to handle precision.
- `highest` (float) — Upper bound of this segment (inclusive). Slightly above 1.0 (e.g. `1.01`) at the end.

But in the code it looks like they're not inclusive:

if value > lowest and value < highest:

I think the documentation is incorrect because based on values in macro.json it makes sense to treat ranges as exclusive.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions